I don't know why but after upgrading Microsoft to the insider preview version. I know, it's always a bad idea to update anything but had to do it to get the new MR Headsets to work...
I downgraded again after visual studio was unable to create any app packages. And it still doesn't work.... tried to repair visual studio and still nothing. I know it's a VS issue because i can't even build older projects which always worked and which i haven't touched.
And now after reinstalling it tells me that the package is unavailable and that i should install windows10 sdk even tho i installed it 100x already.
Edit: I'm also constantly getting this error:
And even after installing the file suggested below nothing works.
I don't get my Microsoft keeps building shit that never works..
Sounds like you should try the last resort:
https://learn.microsoft.com/en-us/visualstudio/install/remove-visual-studio
Use the InstallCleanup.exe to remove all things
There are known issues with using visual studio 2017, when doing hololens development, my stable environment is visual studio 2015 Update 3.0.0 and Unity 5.5 0f1. These I know will work together. Also, if you are trying to use the hololens toolkit, you will also have issues with the new versions of Visual Studio. So you will want to take the Dev branch and not master.
Related
Visual studio 2019 keeps telling me that the Mono version isn't right when im trying to pair to my mac.
I am making a mobile application for iOS in Xamarin.Forms for the last 6 weeks.
This problem didn't show up during this time, but after i updated to the latest version of Visual studio 2019 last week it (like it normally does) asked me to install the latest Mono version.
This became a problem now because the version it wants me to install isn't even released. I am talking about version '6.4.0.208' while the latest version i could find is '6.4.0.198'. Can anyone help me with this problem?
I have tried uninstalling Mono and than installing it again, but this didn't fix my problem.
This is my first time of using Visual Studio 2015 Community with Xamarin, and in using them to create Tizen apps.
In Visual Studio 2015, I chose File - New Project - Blank Tizen App (Tizen Xamarin.Forms Single). The files were generated, but virtually every keyword was not recognized i.e. red underline on them.
What configuration is wrong is my system, and how to fix them?
OK, so I did the following and it fixed this problem (somehow):
1. Uninstalled VS2015.
2. Reinstalled VS2015. I encountered installation failure on Roslyn and NDK-R11C.
3. I Ran VS2015 installer again in elevated mode (Run as Admin) and chose Repair. Roslyn was successfully installed but NDK-R11C was still failed, with the same error as before: Cannot extract the zip file to the target location.
4. Manually I ran the extraction of NDK using windows' default unzipper. I got unclear error message stating that NDK cannot be expanded.
5. Using Norton Commander, Extracted the zip file to the same target location. Success.
6. Ran VS2015, created the blank project. Now NuGet could get the updates, and after that the keywords were properly recognized.
I don't know, though, what was the connection between NDK and Tizen Extension. Maybe the act of reinstalling VS2015 just fixed the problem. At least now I got it now. Thanks all!.
I think it's bug of VS plugin. (it's preview version.)
Project - Unload project and Project - Reload project
I think this should solve your problem.
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).
[Update]
I understand I can use 2015 side by side with VS 2010, but we've had problems just polluting our environment. If there is a chance someone has done this, it could save me a lot of time and energy instead of going with an install only to find out it doesn't work. It's also unfortunate this isn't documented anywhere.
So just like the title says.
To give some more background we're hoping to use VS2015 with our testers to kick start using selenium, but our task/bug management is all on TFS2010.
I don't want to distort the testers' environment, neither can I play with any of our dev machines to try this out physically. A VM will just not really run on our, not so fast machines.
My google-fu didn't get me to far. The VS2015 Express features does mention TFS, but I want to know specifically if it supports TFS 2010. Additionally I found a MSDN page. This talks about the various VS and TFS versions but nothing here about VS Express
Related SO posts I found:
Visual Studio 2015 & TFS 2010 Not specific about VS express or not, no definitive answer
Visual Studio 2015 with TFS 2010 More unrelated, this is about builds going wrong
You should be able to run VS2010 and VS2015 side-by-side, but not on the same solution/project files.
Once you open an older project in 2015, a project conversion will happen. If I recall correctly, project compatibiliy started to stabilizer around VS2012, but don't quote me on that, I'd say it is not likely.
You will NOT be able to open the same project in both at the same time afaik, so it's a one-time shift that'd meet your needs.
As far as task tracking systems go, you could also opt in on VSTS and do a one-time export of your existing bugs/tasks. Shouldn't take you more than a day or so to plan and migrate those over.
You can open the project with VS2015 but it will be upgraded to a newer state. We recently done this and could not go back using VS2010. Otherwise you can version control and keep both projects, i.e. the old implementation and the upgraded one. You could try with VS2015 Community Edition.
You sure can run both versions side by side, but not on the same project. Also, the Microsoft Test Manager that comes with Visal Studio 2015 will not connect to TFS 2010. It tells you that it needs an older version of MTM. I am still working out the kinks on our systems.
Over half of our 50 man development team still uses Visual Studio 2013. Despite this, we would like to use C# 6. So we tried using this solution: https://stackoverflow.com/a/32010632/3997704.
Compilation with Microsoft.Net.Compilers works fine, as does our CI environment. However, Visual Studio shows a lot of errors in the Error List related to C# 6 features. I tried getting rid of the errors by using clean solution, rebuild, restarting Visual Studio and clearing ReSharper caches but none worked.
Even though you install the Microsoft.Net.Compilers package in your project, Visual Studio still uses the C# 5 compiler for the editor. That's why it compiles the C# 6 code, but the editor doesn't understand it. Unfortunately, there is no way to change the compiler editor uses and probably never will be.
So the only way for the full C# 6 support is to upgrade to Visual Studio 2015.