I have already asked this question in the JetBrains forums, but I find that questions are usually answered quicker here than there, so here goes -
The system requirements for ReSharper 6.0 state that it will work on VS 2005 SP1, but it is not recommended. Why is that?
I am using it on VS 2005, and am encountering times (particulary in the option modal) when I try to do something (various things) and it crashes my entire work machine (XP Pro SP3) - not just VS 2005.
The reason why VS2005 is not recommended is because we haven't executed pre-release QA procedures with this version of VS as fully as with VS2008 and VS2010, which, in turn, was due to the decreasing VS2005 user base.
As to why your machine is crashing, this could be investigated further through JetBrains support but in our experience, problems like this, especially with Windows XP SP3, are related to obsolete video card drivers. We've had a few similar support cases that were resolved by updating video card drivers.
Related
Yesterday I upgraded my Windows 10 machine from the Insider Preview to the original release. From that moment on when I try to open solution(even when trying to create new one) in Visual Studio 2013 the program crashes and stops. In the event viewer I found that the crash is due to a heap corruption in the ntdll.dll but that didn't help me. The program runs smoothly in safe mode but crashes every time with every solution when not in this mode.
When this happened I thought that it should be common problem for Windows 10 and VS2013 but I can't find anything relevant in the net for almost a day. Does anybody else experience such issue or similar? Any suggestions will be much appreciated.
Note: I worked with VS2013 and Windows 10 Insider preview for almost a month and experienced no issues. That's why I think the problem is connected with the official release of Windows 10.
You might want to try un-installing VS2013 and then re-installing it on your machine, this works for almost all of the bugs that I encounter when upgrading my OS. Also, make sure you are installing VS2013 Update 5, which was released on the 20th July this year, and not the old VS2013 Update 4 (Or possibly earlier if you are using an old installer) as this may fix compatibility issues, which is likely as Microsoft would have made the most recent version of the software compatible with its latest OS. Even better, try installing Visual Studio 2015 as this will almost certainly be Windows 10 compatible as it is the newest release of the Visual Studio software.
Edit: Don't forget to back up any projects you want to keep before making any changes! This is important as you could easily lose a lot of work when un-installing VS2013.
I'm having graphics issues with Visual Studio 2010. When I open a solution only part of the UI renders. Entire sections like the solution explorer will be missing.
This only happens after I've had Visual Studio running for a while and have opened/closed a variety of solutions.
It "feels" like some sort of a GDI handle leak because the problem goes away once I reboot.
I'm running Windows 7 Ultimate - 64 bit. I've updated my graphics drivers, installed the latest patches, etc. I can't find any postings about this on stackoverflow or doing a variety of Google searches.
Any ideas?
It's a known issue, seems like no fix is coming in SP1, see https://connect.microsoft.com/VisualStudio/feedback/details/575376/visual-studio-2010-code-editor-problems?wa=wsignin1.0 & the workaround described at http://support.microsoft.com/kb/2023207 (disabling HW-Acceleration & Visual Experience adjustment did the trick for me).
Try also to update the graphic driver to their latest version.
The Visual Studio 2010 UI has been rewritten from the ground up in WPF. Myself and a couple of other devs in our team are experiencing the same issues (various hardware and software but my software is the same as yours). In our case closing and reopening VS solves it with no reboot required.
It's a cracking product but roll on SP1.
Running Visual Studio under Administrator (Run as Administrator) fixes the problem for me.
I have a VS2003 WinForms app running on WinCE (running on proprietary hardware so a switch is out for now) and I'd like to know if I can upgrade it to VS2010 (or 2008). In doing so, I lose the option to deploy it to a WinCE emulator. Is this situation just broken, or do I have options.
VS 2008 should work ok.
VS 2010 doesn't support mobile development prior to Windows Phone 7 as stated here.
Best
Adriano
As others have said, go with VS2008 (2010 won't target CF). I worked on WinCE 6 targeting .Net 2.0CF and 3.5CF. 2010 isn't an option (sadly), but at least 2008 gives you the option to use .Net 3.5 which has a lot of features I couldn't live without (linq for instance).
VS2008 is stable and a definite step up from 2005. I am fairly certain 2008 still had the emulator. We never used it as the system was beyond running on the emulator at that point, but I vaguely remember it popping up when I didn't target the actual device.
See also:
ETA on smart device projects for visual studio 2010
VS2010 and non XNA/Silverlight Windows phone dev
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)
Like the title says is there any issues I should be aware of please?
Malcolm
I've done this without problems before. Just make sure you install them in chronological order - installing 2008 then 2005 can cause problems.
Just for reference, VS2010 installs side-by-side as well. I think MS realises that this is a pretty common thing to want to do :)
No, that's completely all right and safe.
You may be interested in "Mixing Visual Studio versions OK" :
Mixing Visual Studio versions OK?
I've got it installed on 2 machines, and I haven't encountered any issues.
I had no problems with this. I installed 2003, then 2008, then 2005.
I have 2005 and 2008 operating side by side. There are no issues from a usability standpoint of Visual Studio itself. The issues tend to be more subtle. For instance, I recently had a problem related the the ASP.NET AJAX extensions 1.0 and compatability after .NET 3.5 was installed as reported here.