You are calling the constructor of the OptionsMonitor<TOptions> class incorrectly. In this case I would have just mocked the IOptionsMonitor<AuthenticationSettings> interface For example using Moq AuthenticationSettings au = new AuthenticationSettings() { … }; var monitor = Mock.Of<IOptionsMonitor<AuthenticationSettings>>(_ => _.CurrentValue == au); ActiveDirectoryLogic _SUT = new ActiveDirectoryLogic(monitor);
There is an open issue on github for this problem. See also the preceeding issue where a possible workaround is mentioned: putting the NavigateTo method into OnAfterRender instead of OnInitialized.
As of 2020 there is no officially supported way to do this. However various people have come up with ways to achieve it, and the current best way is to install a NuGet package prepared by the amazing Teroneko. Then all you need to do is edit your .csproj to update all your project to … Read more
Answer provided by Alex Lyalka : packages were missing dotnet add package Serilog.AspNetCore
You can use the Quartz.Spi.IJobFactory interface and implement it. The Quartz documentations states: When a trigger fires, the Job it is associated to is instantiated via the JobFactory configured on the Scheduler. The default JobFactory simply activates a new instance of the job class. You may want to create your own implementation of JobFactory to … Read more
If you switch your app to target .NET Core 2.0, you can use the Microsoft.Extensions.Hosting package to host a .NET Core console application by using the HostBuilder API to start/stop your application. Its ConsoleLifetime class would process the general application start/stop method. In order to run your app, you should implement your own IHostedService interface … Read more
You need to add a FrameworkReference to your project file instead of a PackageReference as described here. <ItemGroup> <FrameworkReference Include=”Microsoft.AspNetCore.App” /> </ItemGroup> Right-click your project in the Solution Explorer and select “Edit Project File” to open the file and look for the <ItemGroup> section, creating a new one if it does not exist.
I had the same issue with Visual Studio 2022. I could solve the issue by disabling the script debugging in the drop-down of green arrow where we run the project. Please see the following screenshot.
I fixed this error by specifying –project and –startup-project options to Entity Framework Core CLI tools like this: dotnet ef database update –verbose –project CommandService.Data –startup-project CommandService –project means which project contains the DbContext class –startup-project means which project contains the database connection information and other information.
I finally figured it out. For anyone else who runs into this, the steps to fix it are: All localhost certificates must be deleted in certificate manager. They can be found in Personal and Trusted Root The secrets.json file must be deleted. This can be found in \Users\[user]\AppData\Roaming\Microsoft\UserSecrets\ In powershell, re-run dotnet dev-certs https –trust … Read more