Update (2021-01-12): For .NET 5 this is pretty easy. .NET Core 3.0 can even get most of the way there. The original answer was written when .NET Core 1.1 was the newest version of .NET Core. It explains what these new methods are doing under the covers. .NET 5+: byte[] certificateBytes = cert.RawData; char[] certificatePem … Read more
.NET Core doesn’t support Distributed Transactions because it would require a different transaction manager on each platform. It may appear in the future (here‘s the issue in-progress), but for now any Transaction that would require two different resource managers will throw this exception. Instead you can coordinate separate transactions. Have two separate transactions complete their … Read more
This usually happens in the _LoginPartial.cshtml or _ManageNav.cshtml razor view. Eg. @inject UserManager<IdentityUser> userManager Must be changed to @inject UserManager<MyUserStore> userManager The same applies to SignInManager. When registering your own MyUserStore (bad name, should be MyUser) for the AspNetCore Identity, the UserManager<> type will be registered to the ServiceCollection as UserManager<MyUserStore>. Whenever you want to … Read more
For a .NET Core 2.0 console app, I did the following: Create a new file named appsettings.json at the root of the project (the file name can be anything) Add my specific settings to that file as json. For example: { “myKey1” : “my test value 1”, “myKey2” : “my test value 2”, “foo” : … Read more
These instructions from this blog worked for me dotnet dev-certs https –clean dotnet dev-certs https –trust Restart VS
Note that [securestring] is not recommended for new code anymore. While on Windows secure strings offer limited protection – by storing the string encrypted in memory – via the DPAPI – and by shortening the window during which the plain-text representation is held in memory, no encryption at all is used on Unix-like platforms.[1] The … Read more
You can just add <FrameworkReference Include=”Microsoft.AspNetCore.App”/> to library projects .csproj file as mentioned in the docs: <Project Sdk=”Microsoft.NET.Sdk”> <!–… rest of file–> <ItemGroup> <FrameworkReference Include=”Microsoft.AspNetCore.App” /> </ItemGroup> <!–… rest of file–> </Project>
All of the Microsoft.Extensions.* packages target .NET Standard 2.0. That means that you can use Dependency Injection, Configuration, Logging and HttpClientFactory if you add the appropriate package to your application. You need to add Microsoft.Extensions.Http to use HttpClientFactory and Microsoft.Extensions.Http.Polly if you want to use it with Polly To configure HttpClientFactory you’ll have to add … Read more
.Net Core 2 supports a direct reference to external .dll (e.g. Net Standard libraries, classic .Net Framework libraries). You can do it through Visual Studio UI: right click on Dependencies->Add reference->Browse and select your external .dll. Alternatively, you can edit .csproj file: <ItemGroup> <Reference Include=”MyAssembly”> <HintPath>path\to\MyAssembly.dll</HintPath> </Reference> </ItemGroup> You can face with the following error: … Read more
There is likely a better way to do this, but here’s a working example to get you started: Page: @page “/modal-test” <BlazorApp1.Components.Modal @ref=”Modal”></BlazorApp1.Components.Modal> <button @onclick=”() => Modal.Open()”>Open Modal</button> @code { private BlazorApp1.Components.Modal Modal { get; set; } } Component: <div class=”modal @ModalClass” tabindex=”-1″ role=”dialog” style=”display:@ModalDisplay”> <div class=”modal-dialog” role=”document”> <div class=”modal-content”> <div class=”modal-header”> <h5 class=”modal-title”>Modal title</h5> … Read more