Net Standard 2.1 Targeting is missing from Visual Studio 2019 - visual-studio-2019

I just installed the .Net Core 3.0 SDK (both 64 and 32 bit version) and yet, the .Net Standard 2.1 Targeting Pack is not shown in Visual Studio's list. It is going up until 2.0 only. What am I doing wrong?

Apologizing. The problem is that I had to update visual studio.
Interestingly enough, I had Visual Studio open for several hours, and even though an update existed, it didn't prompt me to update, leaving me with the impression that it was already in the most recent version.
I had to run Visual Studio Installer manually to request for an update

Related

Visual Studio 2019 16.18.4 : .NET 5.0 installed yet not available for projects?

I have Visual Studio 2019 updated to the latest current version of 16.18.4 (see screenshot), the .NET 5.0 is installed (see screenshot made in visual studio installer) and yet when creating new projects or then changing
target framework, the .NET 5.0 framework is not available. In the about box Visual Studio displayed .NET 4.8, not .NET 5.0.
To help anyone else who might face a moment of confusion as I did, the following allows creating a .NET Framework Windows Forms project
while the following allows targeting either .NET Core 3.1 or the newer .NET 5.0
and, as said, you can't simply set from VS a .NET Framework project to target the new .NET 5.0.

"This project is incompatible..." after VS 2013 Update 4

After installing Update 4 for VS 2013, I immediately started getting the message
This project is incompatible with the current version of Visual Studio
when I try to open all my MVC projects.
I've tried following advice on older posts, such as changing the version of visual studio, and checking for other updates, but none have worked.
I am using Visual Studio Premium 2013 and have .Net 4.5. It happens to projects that target both 4.0 and 4.5.
This is happening with MVC projects, but it does not happen when opening a simple project containing only .cs files.
Repairing Visual Studio turned out to be the solution.
I believe the initial update was unsuccessful because the C drive was low on space. Clearing up space, and repairing both .Net 4.5.1 and Visual Studio did the trick.

New Asp.Net Project Template Dialog is empty

I have (just reinstalled) Visual Studio 2013 Professional (on Win 8.1) to try and fix this: If I try to create a new Web Project, for either .Net 4.5 or 4.5.1, then I see the screen below.
If I try to open an existing MVC 5 website (one I've just created through that wizard on another machine) - then it works just fine.
Equally, if I set the target framework to 4 then I get the previous MVC 4 template appear, and that works.
If I look in the Microsoft Visual Studio 12.0\Common7\IDE\ProjectTemplates\Web\CSharp\1033\ folder then I see WebApplication45 which appears to contain the content that this project template uses - so why is it broken!?
The machine did use to have VS2012 on it, and I notice that in the list of installed products for 2013 it has 'ASP.Net Web Frameworks and Tools 2012.2' - which I believe is a VS 2012 thing. So I'm wondering if that's interfering with it. But there's nothing on my Add/Remove programmes for this, so I don't know how to uninstall it!
Any help greatly appreciated before I throw my screen through the window :)
Please try the following:
Close VS, open Explorer and go to C:\Program Files (x86)\Microsoft Visual
Studio 12.0\Common7\IDE\PrivateAssemblies
Delete the following assemblies if they exist:
Microsoft.VisualStudio.Web.WindowsAzure.Contracts.dll
Microsoft.VisualStudio.Web.WindowsAzure.Explorer.dll
Microsoft.VisualStudio.Web.Internal.Contracts.dll
Restart VS
In Tools > Extensions and Updates:
Update to lates VS2013 update (it is Update 3 now)
Install if not installed Microsoft ASP.NET and Web Tools
Install if not installed ASP.NET Web Forms MVC 4
Install if not installed MS VS ASP.NET MVC 5 Scaffolding
I solved it by removing all programs connected with .Net development and SQL (just being really cutthroat) - not just Visual Studio; going down my installed programs list from top to bottom:
Visual Studio 2013, obviously
All .Net Framework SDKs and Language Targeting Packs
All Azure tools SDKs (some start with 'Azure', one starts 'Windows Azure')
All SQL Server stuff - possibly too much, but I didn't need them outside of VS
IIS Express
I then rebooted and deleted all remaining Microsoft Visual Studio folders (I had v10, 11 and 12) from Program Files (x86) and all remaining SQL Server folders. SQL is also in the x64 program files, and that's used legitimately by the OS, so might want to skip that one.
I then rebooted again and reinstalled 2013 with Update 3 - and now the new project dialog works as expected.
It's most likely the removal of just one of those things that fixed it (my money is on clearing down the VS folders).
I fixed this by deleting these files from C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\PrivateAssemblies:
Microsoft.VisualStudio.Web.WindowsAzure.Contracts.dll
Microsoft.VisualStudio.Web.WindowsAzure.Explorer.dll
Microsoft.VisualStudio.Web.Internal.Contracts.dll
(based on http://blogs.msdn.com/b/bharry/archive/2014/08/04/vs-tfs-2013-3-update-3-released.aspx#10550199).

Resharper Navigate to MVC View

I recently upgraded to Resharper 8.1 and VS 2013
Before I could ctrl+click on a View to jump to it, but this no longer works. Is there a feature I need to enable to get it back?
PartialView("_MainMenu", viewModel);
Go to Resharper->Manage Extensions and click the Online tab. Then search for Resharper.ExternalAnnotations, and install the package it comes up with.
Finally go to Visual Studio Tools->Options and go to the Resharper->General options page. Click Suspend Now followed by Resume to restart Resharper.
About workaround for previous versions of ReSharper:
You can download package with annotations https://resharper-plugins.jetbrains.com/api/v2/package/ReSharper.ExternalAnnotations/8.1.1000.431 and unpack content of ReSharper\vAny\annotations\ folder to C:\Program Files (x86)\JetBrains\ReSharper\vX.Y\Bin\ExternalAnnotations, where X.Y is your version of ReSharper.
Better first to clean target folder up to avoid annotations duplicates.
ReSharper 8.2.1 (8.2.1000.4556) doesn't support MVC 5.2
EAP for 8.2 is closed
Bug registered
UPDATE:
FIXED: reply about fix from the Resharper team
You need to restart the VS and you will get notification about Update or run it manually from the Resharper => Extension Manager => Updates => Resharper.ExternalAnnotations (like in the Samuel answer)
There still seems to be an issue with ReSharper and navigating to MVC Views or having the QuickFix (Alt+Enter) functionality available on them in the latest (as of this writing) version of ReSharper - v8.2.3000.5176.
My MVC version is 5.2. My ReSharper version is 8.2.3000.5176. When I installed this it seemed to install the ExternalAnnotations that come bundled with the update, also versioned at the same version number.
I can fix the issue by uninstalling the ExternalAnnotations (version 8.2.3000.5176) and re-installing the latest version offered from the ReSharper Gallery (which is version 8.2.2001.1). After a Visual Studio restart, my MVC quick-fixes and View navigation is back.
Strangely, I also get prompted by ReSharper that extension updates are available, and it wants to upgrade my ExternalAnnotations to version 8.2.3000.5176. If I do this (and restart VS) everything breaks again. Downgrading back to version 8.2.2001.1 (and a VS restart) will, however, fix it again.
A number of other people are also reporting this issue on JetBrain's ReSharper blog post that announced ReSharper 8.2.3
So, if you're using MVC 5.2.x and ReSharper 8.2.3, try to downgrade the version of the ExternalAnnotations that you're using and see if that solves the issue.
UPDATE (5th November 2014):
There is now a new version of the ReSharper External Annotations available from the JetBrains "ReSharper Gallery". This new version is v8.2.3001 and I can confirm that once installed, this new version fixes the problem for me!
ReSharper 8.1 just doesn't support MVC 5.1
Latest EAP builds of ReSharper 8.1.1 do.
There should be no problems with running your ctrl+click and no additional configuration (enabling/disabling anything) should be needed. So it is most probably some bug.
Your situation might be connected with the following known issue reported here. It is connected with IntelliSense, not with Resharper directly, but they are both related to problems with navigating in Razor engine when having VS 2013 and newest ASP.NET MVC.
Below the summary of the issue description and some workaround to fix it:
MVC 5.1 Tooling Support and Razor IntelliSense are Still Broken Even
After Installing VS2013 Update 1 RC
Known issue:
If a VS2013 user installed “Microsoft ASP.NET and Web Tools 2013.1 for
Visual Studio 2013” before they install VS2013 Update 1 RC, they won’t
be able to get MVC 5.1 tooling support that comes with VS2013 Update 1
RC.
Symptom:
MVC 5.1 tooling support and Razor IntelliSense are still broken even
after installing VS2013 Update 1 RC.
Workaround:
From "Add/Remove Program", uninstall "Microsoft ASP.NET and Web Tools
2013.1 for Visual Studio 2013" Repair VS2013 RTM Install VS2013 update 1 RC if you have not yet installed it. If you have already installed
this, you don’t need to reinstall or repair it. From Web PI, reinstall
Microsoft ASP.NET and Web Tools 2013.1 for Visual Studio 2013 or
repair Azure SDK 2.2.
try ctrl+B while cursor some where on the View()

Spark view engine - why there is no VS integration in version 1.1?

I downloaded Spark 1.1 release from http://sparkviewengine.codeplex.com/releases/view/27601 and cannot find the msi package for Visual Studio integration promised in docs.
Can anyone explain why?
For VS2008 support, I'm not sure why it's not included in the latest downloads on codeplex, but you can still get the .msi from the download on spark downloads page.
For VS2010, the answer is a little bit more complicated. The short version though is that the visual studio editor changed drastically in VS2010 and the way the old plug-in was providing intellisence is no longer appropriate.
I was able to get the msi installed and working from 1.0.39935.0 with 1.1. I had to close and re-open VS and a few pages.

Resources