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
I have an IOS app-project developed using Xamarin for Visual Studio 2013 which I haven't opened for about a year. Now I have to make some changes to the app and after some problems compiling the project I installed all available updates for Xamarin and Visual Studio 2013, but that only made things worse so I decided to install Visual Studio 2015 and update the Mac and Xcode to the latest version.
Installing VS2015 seemed to solve all my previous problems and I can now compile the project and run it fine (in VS2015), but when I open the storyboard (there is only one in the project) I get a yellow warning bar at the top that says Custom components are not being rendered because problems were detected.
I have no idea why this message appears since I only use standard components (or maybe "components" means something else than those in the Toolbox?). Does anyone know what the reason for this message is, how can I troubleshoot and get rid of it?
I should add that I'm not an experienced IOS developer.
I've been trying to install VS 2015 Enterprise edition on my computer but keep running into an issue. Hunting through SO for the last 24 hours, I've already tried the devenv.exe /ResetUserData & clearing the VS cache fixes, uninstalling enterprise edition and installing professional edition (which still failed for the same reason) and then reinstalling enterprise edition. I've tried deleting the .vs folder before opening the solution, ensuring that the MVC versions in the /Views/ web.config matches the version of the sites web.config (MVC 5.2.3.0).
As of this morning, I've noticed that it only crashes when I try to open a razor view that wasn't created through Visual Studio 2015 (I was using VS 2012 previously, and I'm trying to work on this project in 2015 now that I have a license). I can right-click in the solution explorer to create a brand new view and write anything I want in it with intellisense and save it, and open it back up without any issues.
I get the whole "An exception has occurred, this may be caused by an extension" message and then visual studio restarts if I try to open up a view that was already created through VS 2012.
I've tried looking inside of the log that it provides but I'm a newer developer so I can't really deduce anything from it..I'll attach it if anyone else can make anything of it.
MS VS Enterprise 2015 - Version 14.0.25029.00 Update 2 RC - .NET Framework Version 4.6.01055
I just cleared out the ActivityLog.XML and forced the error to get a fresh set of details - http://pastebin.com/j7RbGJFP
I found the answer in this blog post - https://blogs.msdn.microsoft.com/webdev/2016/01/12/visual-studio-keeps-showing-suggested-extensions/. It has to do with the extensions suggestion - it turns out if you have files not included in your project, you can't view them because of a bug introduced through the extensions suggestion. If you turn that off and include the views in the project, VS won't crash and you'll have intellisense.
I cannot see the story board in Visual Studio 2013, when I open it it tells me
There was a problem rendering this document.
Also in the errors list I have the following:
The clocks on the Build Host and this Machine are out of Sync. Please make sure they are within 3 minutes (UTC) of each other.
Failed to retrieve SDK status from server Xamarin.iOS Extension.
Also the output from the MAC server log tells me:
Error sending iOS designer payload
What can be wrong here?
I was also having a similar problem where I couldn't open the story board in Visual Studio 2012 or 2013 (I didn't have any errors in my error list, just the error when displaying the designer). My setup is dev work in Windows 7 with Visual Studio 2012/2013 with a Mac acting as a Build Host. I had just updated my Xamarin version from 3.0.54 to version 3.3.47 (it had been a little while) and I had created a little prototype app a couple days ago with no problems, so I figured I had killed something with the update.
In my case, the solution was checking for updates in Xamarin Studio on the Mac, where it found several that needed updated. After installing the updates on the Mac side, I was able to display my story board in both Visual Studio 2012/2013 without issues... so I chalked it up to version mismatch issues between the Build Host and my dev environment in Windows.
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()