Have tried upgrading to the professional version of visual studio 2017 v 15.6.0 (Preview 7.0) and installed aspnetcore-runtime-2.1.0-preview1-final-win-x64 and.net core SDK 2.1.4. When I created a new web application I get an error saying 'The current.NET SDK does not support targeting.NET Core 2.1. Either target.NET Core 2.0 or lower, or use a version of the.NET SDK that supports.NET Core 2.1.' When I try to build an existing project I get an error 'The current.NET SDK does not support targeting.NET Core 2.1.
Either target.NET Core 2.0 or lower, or use a version of the.NET SDK that supports.NET Core 2.1.' I don't see '.net core 2.1' in my target framework I don't have global.json file in my computer When I try dotnet -info, I get this c: source dnacloud testappdotnet -info.NET Command Line Tools (2.1.100) Product Information: Version: 2.1.100 Commit SHA-1 hash: b9e74c6 Runtime Environment: OS Name: Windows OS Version: 10.0.16299 OS Platform: Windows RID: win10-x64 Base Path: C: Program Files dotnet sdk 2.1.100 Microsoft.NET Core Shared Framework Host Version: 2.0.5 Build: 17373eb129b3b05aa18ece963f8795d65ef8ea54.
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).
I came across this post on developercommunity.visualstudio.com where a Microsoft support person explains the confusion: 'Thank you for your feedback! We have determined that this issue is not a bug.
The first SDK with.NET Core 2.1 support is 2.1.300-preview1. We know the versioning is confusing which is why starting in 2.1.300, the major.minor versions of the SDK will now be aligned with the major.minor versions of the runtime as well.' In order to get.NET Core 2.1 support for building via the SDK you need to install the SDK with version 2.1.300 at least (since 2.1.2 is NOT.NET Core 2.1). Yeah, confusing.
Welcome to the July 2017 release of Visual Studio Code. There are a number of significant updates in this version that we hope you will like, some of the key highlights include: If you'd like to read these release notes online, you can go to Updates on code.visualstudio.com. The release notes are.
Thank you Microsoft for some lost time on this. I resolved the problem. The cause was that i installed. aspnetcore-runtime-2.1.0-preview1-final-win-x64 and.net core SDK 2.1.4-x64 versions. The installation placed the sdk files in c: Program Files dotnet.
but VS2017 32bit was looking for the sdk files in c: Program Files(x86) dotnet. To resolve this i. installed the x86 version of the sdk and aspnetcore runtime,. set the MSBuildSDKsPath environmental variable to point to the new installation path. deleted all obsolete sdks from control panel The question helped in resolving this issue.
It looks like Microsoft are encouraging better coding practice for those early adopters of latest development software in Net Core 2.1 by removing the capability to use older software where bad habits prevail. Net Core 2.0 and the older versions are almost end of life so should not be being used at all.
1) Microsoft have removed ServiceLocator since widely considered an anti-pattern resulting in difficult to understand code. 2) To improve MVC applications, the AccountController was removed from Authentication/Authorization to encourage use of Razor pages which implement the Single Responsibiity Principle.
It would not be considered best practice to circumvent these changes in order to increase perpetuation of software built to lower software engineering standards in the past.
Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode. Please join us on and in the and organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode.
We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links. Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.
Please create a new report on or with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report. Tom Opgenorth 2017-05-30 15:23:13 UTC Created Project Options - Android: Target Framework combo box disabled. I opened an old Xamarin Studio solution in Visual Studio for Mac that has both Android and iOS projects in it.
I tried to update the Target Framework in the Project Options for the Android project. The combo box that one uses to select the target framework is disabled (see attached screenshot). Also note that if you inspect the Target Android version in Build AndroidApplication, it hints that the target framework version is API 21 (the original API level for this project that I was trying to update) Steps to Duplicate: 1.
Open the PhoneWord-Xamarin solution file 2. Right click on the PhonewordAndroid project, and select Options 3. Click on Build General 4. The Target framework combo is disabled Expected Results: The Target framework combo box should not be disable and I should be able to change the Target framework.