I don't blame him for complaining. He is doing exactly what Microsoft wants him to do, upgrading to the new release, and it has mangled things so badly he has to go into the registry to fix them. This is not how upgrades are supposed to go.

>Why are you even using VS? Every update you complain and complain.
>
>What's your aversion to IIS Express?
>
>
>>I never had to do anything with IIS Express nor have I ever seen it somewhere when working with a Web site or a Web service project in Visual Studio 2013. However, this morning, because of issues causes by some updates, I see that whenever I entered in such project that it created a directory d:\IISExpress. I am trying to get rid of that. By deleting the directory, it did not like it. When entering the project, it complains and the project is not workable. I went into the Registry and bounce back the IIS Express directory to a place where it would not cause any problem based on this page:
>>
>>http://stackoverflow.com/questions/14896911/how-do-i-prevent-iisexpress-my-web-sites-folders-from-cluttering-up-my-my-docu
>>
>>However, this does not work any better.
>>
>>I am trying to understand why Visual Studio 2013, with this update, now need some IIS Express components. I really do not want to have that on my PC. I have IIS 7.5 and that should be enough. IAC, I am not even making reference to local Web sites as the projects are making references to external Web services. So, anyone can explain this and how to get rid of that?