使用任务计划程序在 Windows 上计划 .Net Core 控制台应用程序

Question

是否可以使用任务计划程序安排 .net 核心控制台应用程序在每天的特定时间运行？

Answer 1

I think you will have to set the value for "Start in" while creating the task in task scheduler to your app folder, that is D:\Test\Test1. The app will run in this folder and should be able to find the appsettings file.

Answer 2

Yes, its possible. But theres a trick. For some reason task scheduler mandates full path and filename for hosting process, so you need to enter in the "Program/Script" "C:\Program Files\dotnet\dotnet.exe". Confirmed this on Windows Server 2012 R2 with latest patches. .Net Core program goes into arguments box, no need for full path there. However .Net core program location path is required in "Start in". At least in cases when program is expecting to find some files from its location.

Answer 3

i have similar issue for 2 hours trying to get an answer for this.

All you just need to do for your .Net Core Console App!

• Go to your Task Scheduler
• Go to the tab menu and click on Actions
• Click on New/Edit
• select the dropdown: Action: Start a program
• program/script: "C:\Document\MyConsoleApp.exe"

------> note very important. put in your app path where you have your console app because your task scheduler will have to read to configurations - Start in (optional): C:\Document\

This solved my problem.

Cheers Guys!!!

Answer 4

Create a .bat file with the contents "dotnet myDLL.dll" in actions program/script -> "c:\yourpath\myBatFile.bat" Start in --> "c:\yourpath"

done.

Answer 5

By default the app is going to look at the current folder for the existence of appsettings.json because of the following:

    var builder = new ConfigurationBuilder()
        .SetBasePath(env.ContentRootPath)
        .AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)
        .AddJsonFile($"appsettings.{env.EnvironmentName}.json", optional: true)
        .AddEnvironmentVariables();
    Configuration = builder.Build();

replace the "appsettings.json" with the full path to the file.

Answer 6

Faced the same issue and it ate my hours, solved it by not publishing the project but only by building it. after building the project i just took the content of

MyProject\bin\Release\net5.0

and placed it in

F:\MyFolder

then created a Task in Scheduler, with in Action => Program/script

MyProject.exe

and Start in

F:\MyFolder\MyProject\bin\Release\net5.0

bingo...