Try to add a reference to netstandard in web.config as below: <system.web> <compilation debug=”true” targetFramework=”4.7.1″> <assemblies> <add assembly=”netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51″/> </assemblies> </compilation> </system.web>
Open up the project file (.csproj) and change the TargetFramework to net462 <PropertyGroup> <TargetFramework>net462</TargetFramework> </PropertyGroup>
You haven’t done anything wrong, this is expected to happen. If you want nothing more than your own DLL being added to a new .NET Framework project, you have to target .NET Standard 2.0 for your library wait for a .NET Framework version that natively supports both the API and assembly versions – which is … Read more
As @kiran mentioned in a comment you can solve this by running: Install-Package System.Configuration.ConfigurationManager in NuGet Package Manager
In the project file, you can point target compilation to netstandard with the exact version. Example of Proj.csproj: <Project Sdk=”Microsoft.NET.Sdk”> <PropertyGroup> <TargetFramework>netstandard1.6</TargetFramework> </PropertyGroup> </Project> … Microsoft provides good documentation about targeting types. Dotnet Standard is not a framework or a library, it is an abstract set of instructions: what functionality should have System.Array, String, List, … Read more
In many cases, this can be solved by adding the following code to the csproj file of your test project: <PropertyGroup> <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects> <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType> </PropertyGroup> This forces the build process to create a .dll.config file in the output directory with the needed binding redirects. The reason is that “classic” csproj test projects are true “libraries” and … Read more
In the past, we’ve given developers the recommendation to not reference the meta package (NETStandard.Library) from NuGet packages but instead reference individual packages, like System.Runtime and System.Collections. The rationale was that we thought of the meta package as a shorthand for a bunch of packages that were the actual atomic building blocks of the .NET … Read more
It represents APIs that are shipped as NuGet packages instead of being part of the shared framework for .NET Core. We don’t have the ability right now to identify the different packages and which target frameworks they support on learn.microsoft.com, but it’s something that is in our backlog to solve. So adding that as a … Read more
Add <Deterministic>False</Deterministic> inside a <PropertyGroup> section of .csproj The workaround to make AssemblyVersion * working is described in “Confusing error message for wildcard in [AssemblyVersion] on .Net Core #22660” Wildcards are only allowed if the build is not deterministic, which is the default for .Net Core projects. Adding <Deterministic>False</Deterministic> to csproj fixes the issue. The reasons why .Net Core … Read more
According to .NET docs for the InternalsVisibleToAttribute: The attribute is applied at the assembly level. This means that it can be included at the beginning of a source code file, or it can be included in the AssemblyInfo file in a Visual Studio project. In other words, you can simply place it in your own … Read more