Today a short entry – some kind of a tutorial about solving problems with our hated IDE for Windows OS :) This tutorial will be quite easy and everyone should be able to use it efficiently. For Your convenience I have divided this entry into two parts: How to fix 100% of Your problems? and How to fix 25% of Your problems?. Everything clear? So let’s go!

How to fix 100% of Your problems?

Surprisingly this part is much easier than next one, but a little more challenging in maintenance and in adapting to the new software. Classically, let’s start from entering ‘Programs and functions’ in Your Quick Access bar in Start Menu and pressing Enter. We should now see a list of the installed software on our computer.

Our next step is to find an element with a name starting with ‘Visual Studio 2010’ and select it. Let’s click “Uninstall/Change'” button and follow Installer’s instructions.

When Installer asks us to choose Maintenance task for Visual Studio 2010 we wisely click on ‘Uninstall application’ option and take one’s time until Installer performs all actions required to fulfil this wisely operation. Unfortunately, uninstallation process will take at least as much time as it took while installing. After completing we should restart our computer and began to be happy and wise people, who just dropped the most irritating, buggy and unstable software dedicated for, well… Software Developers and find peace in our souls. Congratulations! You’ve just solved all your problems with Visual Studio 2010!


Ok, but still, I am .NET developer and in my every-day work I need to use some IDE suitable for most common tasks in .NET world. How can I deal with that?

This question is very rational and its answer is quite easy: You have to find another IDE and instantly love it! ;] As for now you can choose from two reasonable products: older version of Visual Studio – VS 2008, which was quite good and with power of ReSharper it can be really helpful and productive. Unfortunately you have to forget about .NET 4.0, which is not supported and can’t be used in previous versions of Microsoft’s IDEs.

However if you really need to use the newest version of .NET you should consider a totally alternative solution: open-source SharpDevelop, which is free, quite functional, extensible, full of nice features and also much faster than VS. Moreover, it fully supports .NET 4.0.

There are of course cons like: quite a lot manual configuration for things which are generally preconfigured in Visual Studio (includes configuration for debugging IIS applications) and problems with the newest Microsoft’s technologies or even lack of possibilities to use them (for example: there are no integrated tools for Windows Azure or Office Sharepoint)

How to fix 25% of Your problems?

In this part we won’t remove anything from your computer – so don’t worry. If you feel comfortable wit the newest version of Visual Studio and you think that it’s not-that-bad then I express my deepest condolences. I can’t hide that these condolences are also for myself, because I still need to use this software in my company and I can’t really change that, however I'm trying ;])

So… What can we do in this situation? Not much, however, there are some things worth remembering:

  • If you use ReSharper, and have installed and enabled extension Productivity Power tools you should turn off one of them. There are known issues with compatibility between JetBrains’ product and this extension. As a result of these compatibility issues Visual Studio may stop responding from time to time.
  • If your code-behind doesn’t generate code-behind for edited controls or pages then you should empty application cache. For your convenience it’s not just a one cache, but 3 different cache folders. For Windows Vista and Windows 7 it will be:
    or generally:
    and other places:
C:\Users\{USERNAME}\AppData\Local\Microsoft\Team Foundation\1.0\Cache   
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files   
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files   

However it’s not a bulletproof method and there are situations where it won’t help at all. In my case, I still need to manually add and edit a designer file for more complex forms and controls; smaller ones (max 40 controls within) are generally automatically updated every save. But the complex ones… it’s a really pain in the ass.


Clearing RFS Cache

ASP.NET controls cannot be referenced in code-behind in Visual Studio 2008

ASP.NET Controls Not Recognized