I have a problem, which I cannot solve. I can't open every cshtml-File in a Visual Studio c# mvc project (whatever which project i tried).
I get the following error Msg (I try to translate to English):
Object reference not set to an instance to an object
Google says, it may be a NullReferenceExeception. But it has nothing to do with my code, because first I can execute the project successfully and second the error occurs in every project (since today).
I just experienced the same issue. It just came out of nowhere, as you described. I even went through a 2 hour repair. That didn't fix it.
However, a coworker suggested this fix.
Visual Studio 2015 not syntax highlighting razor nor Intellisense
I had the same problem, the only fix so far is by resetting all user data (C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe /ResetUserData).
Now I am able to use the real default editing and I get good syntax highlighting again.
The solution that worked for me was from here
Close VS
Delete the content of
%LocalAppData%\Microsoft\VisualStudio\15.0\ComponentModelCache
Open VS
As suggested by #jamez14, if your are using a different version of Visual Studio, just change 15.0 in the path to the version you have.
I faced the following issue.
ISSUE: All .cshtml were not opening in visual studio 17 community.
REASON: Accendently shutdown laptop by power off button while files were open in visual studio.
I tried all the above solutions but none worked.
Following solution worked for me.
Repaired Visual Studio using Visual Studio Installer.
I had the same problem and the issue turned out that I had disabled Razor Language Service Pack.
To re-enable go to :
Tools > Extensions and Updates > search for Razor Language Package and enable. Close VS and reopen.
Running the in console the command: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe /ResetUserData should fix your problem as it resets all user data
This worked for me: Visual Studio 2015 Broken Razor Intellisense
Didn't reset my preferences or caused other side-effects.
It is caused by the version of Razor when updates by NuGet and clean the solution. re-build the project and will open without problems.
I had this same thing recently, resetting profiles and the like didn't work, it turned out that I had some dodgy web.config settings:-
Removing these lines and re-building the project appeared to solve the issue and I could open cshtml files normally:
<add key="webpages:Version" value="4.0.0.0" />
<add key="webpages:Enabled" value="false" />
I found this solution in a github bug thread that mentions many other potential fixes. It seems to be related to updating your version of ASP.Net on an existing project.
Related
As seen in the image bellow, references are not showing up in visual studio.
I was just using visual studio and i closed the project opened some other project and opened the unity project again in visual studio.
But then none of the references shows up and i cant really fix it.
Any ideas on how to fix this?
In Unity Editor try:
Edit -> Preferences... -> External Tools -> Regenerate project files
This problem happened to me, I couldn't solve it, I reinstalled visual again and downloaded c# plugins and module so it worked
The code pair may not be able to compile due to not referencing the relevant library files and namespaces
I'm using Visual Studio 2019 to develop with C#.
Sometimes Visual Studio creates a folder with a gibberish name when I build a solution, like
C:\FNTJ1nkhh1X4r0gk3geH5yIYY8=
This folder only contains the subfolder sqlite3\v1 which in turn contains the following files
db.lock
storage.ide
storage.ide-shm
storage.ide-wal
If such a folder is created, it is created for one certain solution, other solutions don't show that behaviour. Deleting the folder or recreating the solution doesn't help.
To rule them out I already disabled all extensions in Visual Studio but the problem remains.
I've also compared the affected solution file with an unaffected one but didn't find something suspicious.
Has anyone else experienced this and what could be the reason?
After #HansPassant's comment I dug a bit furhter and found that the folder should be located under
%LOCALAPPDATA%\Microsoft\VisualStudio\Roslyn\Cache\RemoteWorkspace
Searching for this location led me to this forum post which confirms this to be a bug in Visual Studio which should be fixed in Visual Studio 2019 version 16.8 preview 3.
Since updating to the most recent version of Unity 5.4.0f3, whenever I doubleclick on a script, it launches both Visual Studio and Monodevelop, but I get an error saying that the this version of VS (Community 2015) is unable to open my project. Monodevelop displays it's own, somewhat less clear error message. Please see the screen shots below.
I can still manually open my script using Visual Studio's file menu, but the intellisense code completion no longer works. Anyone know how to fix this? I have Visual Studio's Tools for Unity installed.
I was having similar issues when doing a clean download of an existing Unity project onto a fresh install of Visual Studio Community 2019.
In the end the issue for me was that, although the correct version of VS Tools for Unity was installed, it was 'Disabled' by default in VS's Manage Extensions dialog (Extensions -> Manage Extensions). Just had to click 'Enable', restart Visual Studio, and all worked as expected again.
Turns out it was an issue with my existing install of Visual Studio Tools for Unity (VSTU).
I found a thread where users had experienced similar problems due to an unsupported version of VSTU running on Unity5.2 and beyond. Unity 5.2+ requires VSTU 2.1 or later for VS to work correctly with Unity, more information for anyone interested is available in the documentation here.
I had VSTU 2.3 installed, but removing and reinstalling VSTU resolved the issue, so there must have been a problem with my install. If anyone else has this or a similar issue you can download the latest installer for VSTU here. Thanks to all who chimed in your responses helped me look in the right place!
Please try following steps:
Delete old *.csproj and *.sln files on project's root folder
Check "Edit > Preferences > External Tools" and make sure you've selected "Visual Studio"
Re-open solution by "Assets > Open C# Project" menu
For me it was enough to right click the solution in Solution Explorer and run "Resolve errors".
I will complete what is said above. I experienced this issue today and it took me a while. In my case it was relative to a new install of the Unity Editor.
For some unknown reason the unity tool used on VS (intellisense) was uninstalled. I had to reinstall this : open Visual Studio Installer, select your project and reach the Gaming section where reside the tool for Unity.
The extension "Visual Studio 2019 Tools for Unity" seems no longer available for download via the extension manager. Luckily I recalled that I saw some game development features in the Visual Studio installer, so I picked that one:
It works for VS 2019 (16.11.11) and VS 2022 (17.2.0 Preview 1).
Visual Studio 2013 (vs) compiles a solution fine when manually building (i.e., it reports "Build succeeded", there are no errors in the error list, and running a program shows the latest changes). However, when vs starts building in the background (for Intellisense?), then errors start to come up for recently added extension methods. The extension methods are underlined in red, and right-clicking on them to "go to definition" results in an error that says "Cannot navigate to [method name]".
Extension methods that were created (in the same classes as the methods listed in the erroneous error messages) previous to when this started happening do not show up in the error messages.
I have done a build clean, to no avail.
I do not have resharper installed.
How do I reset the intelisense cache in Visual Studio 2013? I see instructions for Visual Studio 2008, but not for Visual Studio 2013.
For Visual Studio 2015, my solution didn't have an .sdf file, and restarting didn't help. However, the following steps fixed my problem:
Close Visual Studio (important)
Go to [solution folder]\.vs\[solution name]\v14
Delete the .suo file
Start Visual Studio
It turns out that closing all open files, then shutting down Visual Studio, and restarting fixed the issue. pff!
I had a similar problem that I resolved by deleting *.sdf file in the solution directory. VS2013 will re-create it.
UPDATE This is what I know now: https://stackoverflow.com/a/38708050/90475
After testing all above mentioned solutions simply clean and build worked for me.
In VS2010, the only thing that worked for me was removing and adding the reference again.
Very old question, but it happened to me also with VS2019. I have multiple projects in my solution: right-click on the project -> "Unload Project" for each one, and then reload them. This worked for me.
Clean + Build, or
Close all the files + restart VS + clean
Those didn't work (for me).
I'm trying to create my own VSIX package using the Project template. But when I actually launch it, it doesn't appear to be loading anything. That is, when running the project, it opens up another copy of visual studio, but it doesn't actually load up my plugin. I've compared my plugin to the other sample templates, and I just don't see anything wrong. It seems like it should be pretty straightforward. Are there any other steps besides creating the project that I have to do?
Are you using the visual studio experimental instance for debugging? You can enable this in the Project properties (right click your project and choose properties). Go to the 'Debug' tab and add the following line to 'Command line arguments': /rootsuffix Exp
More information about the experimental instance can be found on msdn.
I spent an entire day trying to reset Visual Studio (2015 Community Edition) by unloading features, deleting the cache directory, using the install to repair -- all with no success.
I finally uninstalled Visual Studio with success. When I initially installed Visual Studio, I had packages errors, like Python, that failed to load, but my Test Explorer worked beautifully. The test Explorer package stopped working in time. After re-installation, everything worked without any package load errors. Also, pay attention to the xml error files, because mine produced exceptions thrown by the package. (The xml error file is reported in the error dialog when Visual Studio informs the package failed to load.