I reecently updated my Unity editor from 5.1 to 5.4.f2f, and my IDEs started misbehaving. I use Visual Studio 2015 Community, and when I updated its Intellisense stopped recognizing all Unity terms. When I open scripts from the Inspector, VS opens nothing first, and open the script with broken Intellisense if I try and open it a second time. Monodevelop also cannot recognize any Unity terms. When I try and "Open C# Project," Visual Studio opens nothing.
The Unity editor also keeps on mentioning in the Inspector that GameObject scripts are missing too.
I'd really appreciate some help here guys. Keep in mind that I've also accidentally pressed the "Publish" button at the bottom of the VS window, but It was after the issue surfaced, so I'm not sure if it has any ties to this.
I think I solved the Problem.
It involved manually opening the Unity project in Explorer and opening the projects .sln file.
Apparently, this is a Windows OS flaw.
I got this answer from This link
Related
This might seem the very definition of a 1st World Problem but it's driving me nuts!
So the right-hand icon is my opened Visual Studio project, and to its left is the icon for Visual Studio 2022. In previous versions of Windows (10) and VS (2019) there was a single Visual Studio icon, which was either plain (no open VS projects) or decorated with a mark at the bottom to show that there was an open project. I'd like to return to that happy place but I can't figure out how. There is no property that I can find on the Taskbar nor in VS itself.
For me, this seems to be a Windows 11 bug. I have the same problem for another program than VS. After unpinning the old icon and pinning the new, the problem is solved for a few days until it occures again. Hope it will be fixed soon.
The answer (so far) seems to be, as #phuzi said, to unpin VS2022. I then closed the project and repinned VS 2022. There is now only one icon - result.
I have a project in Unity 2019.4.0f1 and when I double click on a script in the unity editor it opens as expected in Visual Studio 2019. However despite having Unity Tools installed for VS, the class file does not have any intellitext and non of the objects are colour coded etc. It is as if it has simply opened a text file. If I look in solution explorer is shows nothing and says there are no projects. If I look in windows explorer I can see no solution or project files for the Unity Project...
What is going on? I have done many projects before (on an old laptop) and all of them worked fine... I have never seen this behaviour before.
Ah, I finally found an answer
You have to go to Edit > Preferences > External Tools and Select Visual Studio from the External Script Editor dropdown. Then close VS and double click the script again.
Design View for Xaml on Visual Studio Professional RC 2012 used to work for me. But suddenly stopped for no reason I can figure.
Visual Studio 11 No longer Recognizes Xaml Files.
In properties, it treats XAML files like XML.
In solution Explorer it recognizes it as a xaml file
Right Click -> Design View opens a new Xaml code page
Controls Toolbox shows nothing
My OS is Windows 7 x64.
I have applied all updates up to July 2012 to VS11
I have tried Repairing Visual Studio & Resetting Settings but to no avail.
There is nothing in search or stackoverflow I could find to remedy this.
I have not tried un/reinstalling
Visual Studio 2012 RC designer does not recognize xaml for a Windows Metro app looks identical to my case but my problem suggests the issue is more general than his title.
Reinstalling fixed his issue but does not shed light on this frustrating problem.
Can someone help?
EDIT - Reinstalling nearly resolved the issue. Design view works, toolbox is populated, auto complete is back, XAML is available under tool-> options->text... and control element properties can be viewed.
Everything is normal except for the passing strange fact that XAML Code View no longer does syntax highlighting. This is not suprising since unlike what http://msdn.microsoft.com/en-us/library/bb907395(v=vs.90).aspx expects, there are no XAML prefixed items in the displayed items.
Perhaps relatively minor in the scheme of things but also a very annoying loss.
Suggestion 4 in this link worked for me:
devenv /resetuserdata in Command Prompt.
So at least in my case, re-installing and then the above command cleared all issues. It is possible that resetting user data could have made it unnecessary to re-install but I can't know that now.
I still can't say what caused this but it seems a pretty long tail issue that occurs sporadically and looks to have precursors in older versions.
Check the following:
Tools -> Options
Expand Text Editor -> XAML -> Miscellaneous
Make sure that "Always open documents in full XAML view" is not checked
Or perhaps the default program for opening .xaml files has changed:
Right-click your .xaml file in Solution Explorer
Click Open With...
Select XAML UI Designer
Click Set as Default button
Click OK
EDIT
This does appear to be a known bug with an earlier version of VS11.
If anybody is interested. I had the failure: Could not open XAML and config files in Visual Studio 2012. Now I detected the cause: the Solutions suo files were corrupted after a System Crash. So I (was not sure) rebuilt the sln file in a different Folder and copied the sln and suo files (they are hidden!) to the old Folder. That definitely brought me back the lost functionality. Maybe it is only necessary to delete the old suo files.
Juergen
I had the same issue in Vs 2012 express edition. Solved by running vs2012 command prompt and executing the code
WDExpress/ResetSettings
In Visual Studio 2013 I had a similar issue - I change my build action & from BundleResource to AndroidResource and I was able to get it working.
I downloaded my working last repo from github, and then I opened it to check it worked, which it did. I replaced the xaml, and cs files and it still didn't work. So I just copied all the files in the root,
App.config
App.xaml
App.xaml.cs
MainWindow.Xaml
MainWindow.xaml.cs
packages.config
.csproj
.sln
Everything loaded again, thank goodness.
I just switched to Visual Studio 2010, and now whenever I select something, Ctrl+C to copy, click somewhere else, and Ctrl+V to paste, I get an error message "Cannot navigate to definition." After that, it I try it again, it works. What fantastic new 'feature' should I be turning off to stop this?
Bah, it's a bug in Microsoft Productivity Power Tools for Visual Studio 2010. the "Ctrl+Click Go To Definition" feature. Apparently, when I click a new location and then press "Ctrl+V" - if I do it quickly enough, it interprets it as a Ctrl+Click and immediately tries to trigger a navigation, even if I clicked on an empty space. The error comes because it doesn't know what I'm trying to navigate to (answer: I'm not).
I have/had similar issues in VS 2012 (Premium).
I've tried the following:
removed all bin and obj folders from project's folder: works most of
the time.
repaired VS 2012 (add/remove bugrams (programs) > repair). Didn't
help much.
Close and opened VS 2012: didn’t help much either.
I've noticed than I couldn't open only files that weren't check-in in
TFS. I check-in them and then VS started working normally.
Dunno if this issue will appear again tough.
Hopefully this would help someone.
BR
you can remove the GoToDefProPack.dll file from the following location:
C:\Users(myUserName)\AppData\Local\Microsoft\VisualStudio\10.0\Extensions\Microsoft\Productivity Power Tools\10.0.20318.14
to disable this feature completely.
Picture says it all, it should currently be showing a file but as you can see its having issues drawing the content of the file.
I have unloaded all addons and restart visual studio.
If it mathers the previus project was a VS 2k8.
New Info:
If i wait a good 5min ( I have a Quad core I7 with 6gb ram, 295gtx. VS is running from a SSD).
It will load the text, but im unable to "edit", as it will have loaded some document (.cs ) but when i select the one i want to edit it not realy open that file.
It can best be described as visual studio having a 5min lag.
I had this precise bug. I would open files from the solution explorer but the editor window would either not appear, only 1-2 lines of 100+ line files would display, or the file would display but I could not scroll or otherwise edit the file. Some parts of VS were working, i.e. little tooltips would appear if I moused over the right part of the (invisible) text but I obviously couldn't do much in this state.
I have a lot of VS stuff installed so I thought it was some sort of plugin or extension that was causing things to go screwy. These installed items include:
Visual Studio 2010 10.0.30319.1
ReSharper 5.1.3000.12 (JetBrains)
DevExpress DXCore 10.1.5 (free community edition)
DX Source Outliner (reason for DXCore, from sbohlen)
Tabs Studio 2.0.6 (www.tabsstudio.com)
Productivity Power Tools 10.0.11019.3 (Microsoft)
Snippet Designer 1.3.0 (Matt Manela)
I solved it (2/18/2011) by Tools... Extension Manager... disabling the Productivity Power Tools and Snippet Designer. No idea what was going on but this fixed it for me and I was back to work. Probably something in the system drawing and/or display options.
EDIT
The issue continues. Unfortunately it is intermittent and I have not be able to reproduce it reliably. Now the suspects are the BugShooting and CaptureWiz screen capture tools. I've had the behavior show up and then disappear in and around the time of logging bugs with them.
2nd EDIT
The issue continually continues. I have not yet been able to determine the cause but usually quitting VS and restarting resolves the issue(s). Other parts of the behavior includes the menu options (File, Edit, View, etc.) not operating properly as they show only the highlight but not the actual menu items. The solution will build and run just fine, but things still won't show up properly.
I had a similar issue whereby VS2012 was telling me that I had active (open) files, but the text editor was not displaying them. Clicking on the file(s) in the solution explorer seemingly did nothing. Alt + Tab just cycled through the open files, but still, nothing rendered on screen.
I solved it by clicking on the "WINDOW" menu item and then"Close All Documents". Visual Studio then behaved as expected and opened (and rendered) the files correctly.
This bug was created by mumble 1.2.x, but is fixed in the snapshot versions of 1.3.x. YOu can likely get simular bugs by other software that does DirectX overlay.
I had the same issue in Visual Studio 2012. It was fixed by running a repair of Visual Studio 2012 via Add/ Remove Programs.
The following had no effect:
Closing and reopening a solution
Opening different file types
Restarting Visual Studio
Adding and removing plugins
Resetting options via the 'Reset all Settings' option in Visual Studio's 'Import and Export Settings'
Rebooting windows
I had this problem in Visual Studio 2013. Problem was: extension "Regex Tester". I had to uninstall this extension.