github-actions[bot] on v4.5.0
jeremydmiller on master
option to also clear state on a… (compare)
github-actions[bot] on v4.4.0
jeremydmiller on master
new extension methods for rebui… (compare)
github-actions[bot] on v4.3.1
jeremydmiller on master
changing the resources display … (compare)
github-actions[bot] on v4.3.0
jeremydmiller on master
Workaround for extension servic… (compare)
github-actions[bot] on v4.2.0
dependabot[bot] on npm_and_yarn
Bump prismjs from 1.25.0 to 1.2… (compare)
jeremydmiller on master
ran the stdocs to vitepress con… *mostly* converted docs to Vite… deleting obsolete stdocs docume… and 9 more (compare)
NetCoreInput.cs line 44
would be my guess, but I'm not sure what the intent is behind the code.
NetCoreInput
never has a logger value and does not do anything out of the ordinary. Something that Oakton does while loading configuration from appsettings.json interferes with how Serilog configures sinks and forces Serilog to use a SilentLogger as described by serilog/serilog#562 and shown below.
preserveStaticLogger: true
parameter described here.
RunOaktonCommands
(from Oakton 3.1.0 NuGet package), the site starts and then stops immediately.That error was:
Determining projects to restore...
C:\inetpub\wwwroot\iss.local\InnovativeStaffSolutions.EmployeeManagement.Web\InnovativeStaffSolutions.EmployeeManagement.Web.csproj : error NU1605: Detected package downgrade: Oakton from 3.0.0 to 2.0.5. Reference the package directly from the project to select a different version.
C:\inetpub\wwwroot\iss.local\InnovativeStaffSolutions.EmployeeManagement.Web\InnovativeStaffSolutions.EmployeeManagement.Web.csproj : error NU1605: InnovativeStaffSolutions.EmployeeManagement.Web -> Lamar.Diagnostics 3.0.2 -> Oakton (>= 3.0.0 && < 4.0.0)
C:\inetpub\wwwroot\iss.local\InnovativeStaffSolutions.EmployeeManagement.Web\InnovativeStaffSolutions.EmployeeManagement.Web.csproj : error NU1605: InnovativeStaffSolutions.EmployeeManagement.Web -> Oakton (>= 2.0.5)
Failed to restore C:\inetpub\wwwroot\iss.local\InnovativeStaffSolutions.EmployeeManagement.Web\InnovativeStaffSolutions.EmployeeManagement.Web.csproj (in 792 ms).
RunCommand
to the non-async
version fixed the issue for me. I tried a few variations with the async
version but couldn't get it to wait without the Unloading
event handling. However, I also saw that the issue went away after I added Serilog. So it apparently has something to do with how the internals of ASP.NET 5 are being configured.
class Program
{
static int Main(string[] args)
{
// As long as this doesn't blow up, we're good to go
return CommandExecutor.ExecuteCommand<NameCommand>(args);
}
}
DefaultCommand
usage here: https://jasperfx.github.io/oakton/documentation/bootstrapping/