The reference assemblies are correct. In .NET Framework 4.5, these properties were abstract. They were changed to virtual in .NET Framework 4.5.1. It appears you’ve uncovered a documentation bug. As you probably have already guessed, the difference between the two System.Data.dll assemblies you are observing is due to how .NET Framework separates reference assemblies and … Read more
I have loaded core project to the VS 2017 RC Community and open *.csproj in text editor. Just delete teg <RuntimeFrameworkVersion> and replace <TargetFramework>netcoreapp1.1</TargetFramework> to <TargetFrameworkVersion>v4.6.1</TargetFrameworkVersion> And after all in project properties set to any another framework and reset back (VS reload and repair *.csproj file).
With the WebAdministration module loaded try this on a pool that you’ve created: Set-ItemProperty IIS:\AppPools\<pool_name> managedRuntimeVersion v4.0
This should give you all the answers you want: https://en.wikipedia.org/wiki/.NET_Framework_version_history#Overview Due to the fact that new versions of .NET are being released all the time I felt it would not be correct to try to embed the history into this answer, but merely direct you to a source which is updated.
Download Microsoft.NETFramework.ReferenceAssemblies.net45 from nuget.org Open the package as zip copy the files from build\.NETFramework\v4.5\ to C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5 For more details: Building a project that target .NET Framework 4.5 in Visual Studio 2022
In PowerShell you can use the following to get the target runtime: $path = “C:\Some.dll” [Reflection.Assembly]::ReflectionOnlyLoadFrom($path).ImageRuntimeVersion I adapted this to PowerShell from Ben Griswold’s answer. If you want to know the target framework version specified in Visual Studio, use: $path = “C:\Some.dll” [Reflection.Assembly]::ReflectionOnlyLoadFrom($path).CustomAttributes | Where-Object {$_.AttributeType.Name -eq “TargetFrameworkAttribute” } | Select-Object -ExpandProperty ConstructorArguments | Select-Object … Read more
Please make the next steps Clean solution Clean folder “packages” Delete folder “bin” Delete folder “obj”
I think the solution might be this issue on GitHub: Try add netstandard reference in web.config like this:” <system.web> <compilation debug=”true” targetFramework=”4.7.1″ > <assemblies> <add assembly=”netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51″/> </assemblies> </compilation> <httpRuntime targetFramework=”4.7.1″ /> I realise you’re using 4.6.1 but the choice of .NET 4.7.1 is significant as older Framework versions are not fully compatible … Read more
C# language version history: These are the versions of C# known about at the time of this writing: C# 1.0 released with .NET 1.0 and VS2002 (January 2002) C# 1.2 (bizarrely enough); released with .NET 1.1 and VS2003 (April 2003). First version to call Dispose on IEnumerators which implemented IDisposable. A few other small features. … Read more