Tags down


Can ASP.NET target .net core?

By : Stuart Wighton
Date : July 29 2020, 10:00 AM
I hope this helps . The Bit.Core project targets
.Net Framework 4.6.1 .Net Core 3.1
code :
<Project Sdk="Microsoft.NET.Sdk">

  <Import Project="../Server.Build.props" />


    <PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="3.1.2" />
    <PackageReference Include="Newtonsoft.Json" Version="12.0.3" />
    <PackageReference Include="System.ComponentModel.Annotations" Version="4.7.0" />
    <PackageReference Include="System.Configuration.ConfigurationManager" Version="4.7.0" />
    <PackageReference Include="Autofac" Version="5.1.2" />
    <PackageReference Include="System.Net.Http" Version="4.3.4" />


Share : facebook icon twitter icon

Build ASP.NET core application to target dot net core framework 1.1.0

By : Shobhit Zakhmi
Date : March 29 2020, 07:55 AM
I hope this helps . You can set the 1.1.0 property in your .csproj. This will tell the SDK to specifically target 1.1.0 instead of the implicit 1.1.1.
See my answer to a similar question on how to set this property automatically.

Choosing between full .NET framework and .NET Core as ASP.NET Core target?

By : M N
Date : March 29 2020, 07:55 AM
seems to work fine .net Core libraries are actually .net standard libraries. So when you create a .net standard library it can be referenced by full framework classes, but only if the version of .net standard you are using is correct. Sound confusing?
In simpler terms, take a look at this chart here https://github.com/dotnet/standard/blob/master/docs/versions.md

The Current .Net SDK does not support targeting .Net Core 2.2 Target .Net Core 2.1 or Lower

By : RBH
Date : March 29 2020, 07:55 AM
I hope this helps . https://developercommunity.visualstudio.com/content/problem/387549/net-22-loast-afte-upgrading-to-1592.html
seems that the latest release turns off the use of preview, "Use previews of the .NET Core SDK" option under menu -> Tools -> Options -> Projects and Solutions -> .NET Core

The current .NET SDK does not support targeting .NET Core 2.2. Either target .NET Core 2.1 or lower

By : user3490841
Date : March 29 2020, 07:55 AM
Hope this helps It's very important and not necessarily obvious, but you'll want to make sure that you explicitly target the 2.2.1xx version when running Visual Studio 2017 as the build versions differ between Visual Studio 2017 and 2019:
Visual Studio 2019 - 2.2.2xx Visual Studio 2017 - 2.2.1xx

The current .NET SDK does not support targeting .NET Core 2.1. Either target .NET Core 2.0 or lower, or use a .NET SDK t

By : Alejs Subía
Date : March 29 2020, 07:55 AM
will be helpful for those in need The problem here is that Microsoft confused a whole lot of people with how they numbered their .NET Core SDKs.
In the original poster's message the path C:\Program Files\dotnet\sdk\2.1.100\ DOES NOT appear to represent the .NET Core 2.1 runtime (but you'd think it does).
Related Posts Related Posts :
  • 'Procedure or function 'GenerateTest' expects parameter '@questionnaireID', which was not supplied.'
  • What are effective options for embedding video in an ASP.NET web site?
  • Visual Studio "Unable to start debugging on the web server. The web server did not respond in a timely manner."
  • Tracking state using ASP.NET AJAX / ICallbackEventHandler
  • ASP.NET Display SVN Revision Number
  • ASP.NET URL Rewriting
  • Easy way to AJAX WebControls
  • How do I define custom web.config sections with potential child elements and attributes for the properties?
  • Are Multiple DataContext classes ever appropriate?
  • Triple Quotes? How do I delimit a databound Javascript string parameter in ASP.NET?
  • ASP.NET built in user profile vs. old style user class/tables
  • Bandwith throttling in IIS 6 by IP Address
  • ASP.Net Custom Client-Side Validation
  • Checklist for IIS 6/ASP.NET Windows Authentication?
  • shadow
    Privacy Policy - Terms - Contact Us © voile276.org