I work in a corporate environment where updates are pushed to indiscriminately to developer machines. I'm working in Windows 7. Very recently I have begun receiving VS 2013 compiler dependencies warnings.
When I saw the warnings, I ran VS 2013 Update 5. But the warnings persist.
Should I worry about these warnings?
If I should worry, how can I resolve them?
Thanks
I have abandoned this question. I realized that it would be better to migrate to VS 2015 rather than trying to shoehorn in the code needed into VS 2013.
Related
I've been working on a C# MVC application in VS2015 with no problems. Recently I've upgraded to VS2017. I opened the same project in VS2017, but whenever I try to run it, I get the exact same error verbatim as described in
this question VS2017: The debugger is not properly installed. Cannot debug the requested type of code
I've followed every single piece of advice in that thread. I've also performed a repair on my installation - but none of the suggestions worked for me.
It's August now, so I wonder if anything has changed and if there is a solution now.
I have a feeling the problem is probably due to the differences between VS2015 and VS2017 - this was originally something built in VS2015 after all.
I also had issues few months ago when i upgraded VS2015 to VS2017 and one of my big project that i was running on visual studio 2015 stopped working. That project had seveleral class libraries and DLLs added. VS2017 asked me to installed required libraries/ddl one by one, which i did and still didn't work.
So what I did was, Uninstalled the upgraded version of visual studio 2017 and re-installed the complete visual studio 2017 from MSDN website (selecting the default selection of features). And then i loaded my Project in VS2017 fresh copy and it worked.
I suggest you to try the same
I'm having this question since a month and I'm not able to test it, so i want to ask here if someone have met this situation. Since there is no official release of the new Visual Studio 2015 and it's on RC now ,I'm interested in does someone know if VS 2015 and VS 2013 could work together? Will be the code "infected" if both sides commit something together? Thanks in advance!
In theory yes, in practice no (or at least your results may vary). VS is designed for side by side installations. For consultants it is very common to have multiple versions of VS installed to match the environment of the client.
That being said, RC is pre release software and bugs are to be expected. Nobody can guarantee you won't have problems. VS is a huge and complex codebase. Throw in the number of permutations of possible plugins and extensions as well as environment conditions and there is always a chance of breaking. Just because it didn't blow up on someone else's system doesn't mean you won't have problems.
When I installed VS 2015 CTP6 a few months ago it broke an install of VS 2013 on the same machine. VS 2015 CTP6 installed without error but trying to "login" (Microsoft's new annoying way to infect all software with a user login) hung and became unresponsive. Upon restart devenv.exe complained about corrupted user settings and even before I tried I had a bad feeling that VS 2013 blew up as well. I was right and it took a reinstall to get it working.
Now on the other hand I installed VS 2015 RC side by side on a machine with VS 2010, 2012 and 2013 without any issue. Does that mean you are guaranteed to not have a problem? Of course not. It is pre-release software. If this is a mission critical machine and you don't have the time to potentially spend a few hours reinstalling VS 2013 I would install it in a VM. If it isn't mission critical or you have the time to reinstall if necessary then roll the dice. Honestly you "should" be fine, the RC is pretty stable but you never know.
You should be fine - you'll be using an existing code-base and as long as you don't change the .NET version in the properties, it will compile the same.
However, if you do want to check out the new vNext solutions, you'd have to specifically select the project template in the new project wizard.
These projects are run on the new DNX runtime (which is still evolving and subject to change)
Side by Side. Visual Studio 2015 (even RC) works seamlessly side-by-side with Visual Studio 2013.
See BUILD 2015 News: Visual Studio Code, Visual Studio 2015 RC, Team Foundation Server 2015 RC, Visual Studio 2013 Update 5
or the official guide in the documentation
you might follow the links inside for details about how to configure the target language specific frameworks.
I have just installed VS 2013 RC2 and TypeScript refactoring stopped working. It disappeared from context menu, and pressing Ctrl+R, Ctrl+R gives the following error message:
The key combination (Ctrl+R, Ctrl+R) is bound to command (.Refactor.Rename) which is not currently available.
I have tried restarting VS, didn't help. Any ideas, workarounds?
Edit:
I have submitted a bug to Microsoft. Please upvote it if you have the same issue:
https://connect.microsoft.com/VisualStudio/feedback/details/860463/typescript-refactoring-stopped-working-in-vs-2013-rc2
Microsoft posted the following answer to my question on MS Connect. Seems that while refactor/rename was available in VS Express Edition with TypeScript 0.9, in TypeScript 1.0 it's only available from VS Pro upwards.
Posted by Microsoft on 19/05/2014 at 09:25
Thank you for reporting this issue.
Refactor/rename and NavigateTo are features that are found in the Pro+
versions of TypeScript in Visual Studio 2013. The Pro+ tools are aimed
at helping users work with larger codebases, so there is a focus on
building up tools to help support those codebases in those versions of
Visual Studio. We're working to continue to refine to make the
experience best across both Express and Pro+, with the right features
to help users who want to learn TypeScript and those who want to move
to using TypeScript in larger projects.
For me it happened because of resharper conflict. I uninstalled resharper and restarted visual studio
I cam across this question here on SE:
Can Visual Studio 2012 be installed side-by-side w/ Visual Studio 2010?
According to one comment with a good amount of upvotes, having 2010 and 2012 installed at the same time can present issues. I then came across this MSDN page about 2013:
http://msdn.microsoft.com/en-us/library/hh266747.aspx
If you use Visual Studio 2013 together with Visual Studio 2012 or Visual Studio 2010 SP1, you can [blah blah]
That suggests that 2013 can be safely installed along with VS2012. Can anyone confirm?
Take a look at Brian Harry´s Blog post announcing Visual Studio 2013.
VS 2013 can be installed side by side with previous versions of Visual Studio or, if you have a VS 2013 pre-release, it can be installed straight over top of the pre-release. TFS 2013 cannot be installed side by side but can also be installed over top of either a previous version (TFS 2012 or TFS 2010) or a pre-release.
Looks like you can, yes.
You can install this version of Visual Studio on a computer that
already has an earlier version installed.
http://msdn.microsoft.com/en-us/library/ms246609%28v=vs.120%29.aspx
Only issue I can see is during uninstallation, where the file associations may get lost.
I was having two installation on my computer. Really no problems.
From personal experience, I've come across multiple issues with using Visual Studio 2012 and prior, while a VS2013 installation exists on a machine.
Some of the issues include built executables failing to launch (double clicking .exe does nothing, but debugging them in VS launches them), and inability to compile solutions that mix C# and C++ projects.
I would avoid 2013 until these issues are resolved, as just having it installed on a machine breaks older code, even if you don't use VS2013.
There are some minor (compatibility) issues between using both VS2010 and VS2012 on the same Solution, but simply having VS2012 installed on your machine won't effect anything in VS2010.
There may be compatibility issues with 2013 Community edition. I had VS 2012 Ultimate and VS 2013 Express installed and working without any issue, but as soon as I installed VS 2013 Community, my VS 2012 Ultimate install has been behaving unusually. When I first open VS 2012 U, there is a really long load time. When I perform some action (open a file, select a menu option, anything actually) I have to minimize and maximize VS 2012 U for the screen to refresh. I am still trying to figure it out myself - so if anyone has a solution, please share.
Does Visual Studio 2010 RC play nicely with Visual Studio 2008?
I am wondering if I need to setup a Virtual Machine to play with VS 2010 or if I can just install it on my Dev machine.
If it messes up VS 2010 then that is sad but ok. If it messed up VS 2008 then I would be in trouble.
Has anyone tried this out? Does it work well? Poorly?
Thanks for any answers.
I've had no problems. Microsoft has designed the last several versions of Visual Studio to be able to co-exist side-by-side.
That said, VS 2010 is an RC, so it is still a pre-release. And even after it goes RTM, it's still a complex product and like any complex software install there can be bugs. I wouldn't expect serious problems, but there's always the fraction of a percent that do run into issues. So I'd still plan to install it on a day when you'd have cycles to deal with potential issues (if nothing else, installing it on my machine that hadn't had OS updates installed in a while required at least 2 reboots).
Yes this works and is a supported scenario. My advice is to install 2008 first then 2010. This is the setup i have on multiple computers.
has worked for me without any issues so far. I would follow JaredPar's advice though, install 2008 first, then 2010.
I never trust the "plays nice with others" claims because I've been bit by it before. They supposedly co-exist, but I still put it in a VM.
See this blog post.
Visual Studio 2010 / .NET Framework 4 RC Ready for General Download
I haven't installed it on my machine but my manager has and after we looked at it we decided it's best not to go there yet for two reasons:
1) We have to go through the whole conversion process again, which after our experience with 1.1 -> 2.0 wasn't very enticing.
2) We caused an error within the first couple minutes of playing around that worked fine on VS2008 leading us to believe it's not quite ready for primetime yet anyways. (It was adding a method in the class diagram that caused VS to crash for some reason).
Just my two cents though.
edit: I just found another great example, fifth one down: http://thedailywtf.com/Articles/Tell-a-programmer.aspx
I've had no problems either. And I didn't with VS2010 beta 2 and VS2008 either.
I have both of them on my machine, so far no problems
I havent go into too much testing with my VS 2008 projects in 2010, but it does look like it works fine with VS 2010 RC.
Also, both versions seem to run fine on my machine. (I have also VS 2003 on my local as well)
Bearing in mind its the Release Candidate version, is should be very reliable in this area.
I've run into an error with IIS and VS2010 -- it's solved by re-running the .NET 3.5 version of aspnet_regiis.
http://social.msdn.microsoft.com/Forums/en-US/vsprereleaseannouncements/thread/44dfcf76-bede-4f96-a556-b219a18b6116
I installed 2010 with 2008 already installed. I had tons of hangs, crashes and general malfunctions. Reinstalling 2008 didn't help until I removed every trace of 2010 from registry.
I've installed 2010 with 2008 on this machine for silverlight development.. I haven't noticed any problems except for file associations all goto the 2010 version rather than what I'd prefer opened in 2008 by default. (2010 to me is much slower than 2008)