I was developing a website using the ASP.NET platform on Visual Studio 2015 Community with Updates 1. But I tried using design mode and the IDE was so slow!
I could not do anything else. I've tried to repair, but after 15 hours, nothing happened. So, I've prefered the uninstall, but it wasn't had progress. Is there anything that I can do about this?
You could try the Revo Uninstaller Software, this looks for registry entries of the Program and removes them to.
Havent used it since a long time, but removing some toolbars without proper uninstallers it did its job just fine.
Another Tip:
Visual Studio creates a System Recovery Point before you install/uninstall/repair it. Try to restore your PC to that should be the easiest method.
Related
Just recently uninstalled VS2017 RC and installed VS2017 RTM.
We have a Windows Service solution which includes a Setup project.
When I build this in Visual Studio 2017, somehow it's triggering something in the installer for Visual Studio 2013 (which we're still using), as I get this popup appearing:
It's fairly reproducible, but I have no idea where to start with this one.
Any ideas how to stop it happening?
It didn't happen before with the release candidate.
EDIT:
So, several VS2017 updates later, this problem had got a lot worse, as it was stopping me building the setup project completely. Previously I was able to click cancel as in my first screenshot, but at VS2017 v15.3.3, it wouldn't cancel, and if I let it run, it hung at:
So this forced my hand somewhat. I've accepted #PhilDW's answer as he led me straight to the main clue, but I'll also add an answer of my own with more detail.
As in PhilDW's answer, I checked the event log, and found this:
Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature
'Visual_Studio_Professional_x86_enu', component
'{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed. The resource
'C:\Windows\Microsoft.NET\Framework\URTInstallPath_GAC\' does not
exist.
A little Googling, and I found this MSDN blog entry:
Workaround
We are consistently seeing this issue caused by a missing directory,
C:\Windows\Microsoft.NET\Framework\URTInstall_GAC (or
%SystemRoot%\Microsoft.NET\Framework\URTInstall_GAC).
To work around this issue,
Open an elevated command prompt.
Type: mkdir %SystemRoot%\Microsoft.NET\Framework\URTInstall_GAC
Note that the folder name isn't the same as in my case. I didn't notice this initially, and creating the folder didn't cure the problem.
However when I created the actuall folder referenced by the event log message, the problem went away, and I can now build my setup project without messages about VS2013.
It's a repair of Visual Studio 2013 because Windows thinks the install is broken (registry entries or files not as in the original VS 2013 install). If you look in the Windows Event log, Application, there should be some MsiInstaller log entries that tell you the product (by ProductCode guid) and the broken component (by component guid and file or registry name). This might help identify what's going on, but not necessarily have a clue to a fix. If it's a setup project it might be a conflict with mergemodule Dlls or prerequisites, some of which come from the current SDK.
You don't say if you're letting the repair complete, in the case that it's just an isolated occurrence.
hoping somebody has run into this issue and knows a fix as it's driving me up the wall...
I mainly write web applications at my place of work and we've recently got our upgrade to Visual Studio 2015 Professional (Version 14.0.23107.0).
Since my first fresh install (and subsequent reinstalls) whenever I attach to a process to debug all my code windows disappear. If I click on the "Windows" menu bar item then I can still see those that have disappeared, but when I try to open them they refuse to appear.
If a breakpoint was get hit on one of those "missing" files then I would get the standard "browse to find source" window you often get when using 3rd party libraries.
What I have to do at the moment is place all my break points, close all my windows and then attach to my w3p.exe process. It's pretty annoying and I was wondering if anyone else had encountered this?
For reference, I'm using IIS 7.5.7600 on Windows 7 Professional on SP1.
Below is an example image of what I see when, on a brand new ASP.NET 4.6 project, when I place a breakpoint on the Index method in HomeController. If I click "Browse and find HomeController.cs" absolutely nothing happens.
Does anyone know what I can do to alleviate this issue?
EDIT: Also happens when debugging straight from Visual Studio using IISExpress
I have a ASP Project running Visual Studio 2013 having very bad Performance while debuging/running the Project. The same Project running on a normal IIS Server is super fast with no Problems. Other Projects are running also super fast with no Problems (also on VS2013).
I have already tryed the following:
Delete All Breakpoints does nothing.
Debug or Release version, doesn't matter.
start without Debugging has the same problem.
Putting my project on a full IIS implementation on a web server runs it super fast with no problems.
Clean Solution, or deleting the .suo also do nothing
comment all the CodeBehind and the JavaScript
the solution with symbol loading from Visual Studio debugging/loading very slow also dont work.
Another often mentioned solution is to deactivate Intellitrace, but I don't found how to do that in VS2013 (the Intellitrace MenuItem in the Tools/Options Menu is missing)
There are many empty ScriptDocuments created while running, dont know if that has anything to do with the Problem.
Thanks for any Ideas!
This may sound strange, I had the same problem and tried all suggestions I found on the internet. The cause for me was I has a blank DVD in my drive. I found this by looking at where Visual Studio was trying to load the symbols from "my d drive (dvd)". After I ejected the blank DVD it was back to normal. This was very strange but just saying, check where VS is trying to load the symbols from in the output window. Hope this save someone from running round in circles.
In Visual Studio 2010 SP1, automatic outlining is not enabled for ASPX files when I open them. For each file opened, I need to click Edit / Outlining / Start automatic outlining, which is extremely annoying. This step is not necessary when code-only (non-ASPX) files are opened.
I use a few extensions, all of them from MS, including Power Tools, the JavaScript tools, etc., and I thought that maybe they were causing the problem, so I disabled all of them and restarted VS, but the problem still exists.
I did not have this problem with VS2010 (no SP) on Win XP Pro, which I used for about 18 months, but I recently did a clean install of Win 7 x64, VS2010, and VS2010 SP1, and now I have this issue.
Any ideas?
This worked for me:
In the registry, look here:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\HTML Editor
for a value named OutlineHTMLOnFileOpen. Mine was set to 0, change it to 1. Make sure you do this while VS is closed, as it saves this value out on exit and will change it back.
I had this issue and it was driving me crazy all week!!
Finally managed to fix it really easy:
Make sure the registry value for OutlineHTMLOnFileOpen is set to: -1
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\HTML Editor
OutlineHTMLOnFileOpen = -1
Open VS then open an aspx file.
Press CTRL M then M again while keeping the CTRL key depressed.
Press Ctrl+ M M
Wait a few moments and the automatic outlining engine will start.
Restart VS and it should auto kick in again when you open a file.
I had the same problem and went through and disabled my extensions. Once I disabled the Javascript Addins from Microsoft (That give the outlining and brace matching), I found I was able to change the registry setting and it didn't set change back. I'm going to reinstal the addin to see if it was the actual cause.
I posted the same question at the MS forums, and was told to do the following, which I have not yet had time to try, but I thought I would add it here for now:
Please try to create two new project (one is the same type project as
your previous project, one is another type project.) see whether this
issue still exists.
If this issue still exists, you can try the following solutions:
If we reboot the operating system to safe mode, do we have the
problem? This can help to isolate whether any other applications are
interfering with Visual Studio. Note that some features (like IIS) are
not available under safe mode. Please check whether this can apply or
not. In addition to safe mode, we can also suggest “clean boot”:
http://support.microsoft.com/kb/310353 .
If we create a new user account, do we have the problem? This can
help to isolate user profile corruption related causes.
If we use “devenv.exe /resetsettings”, does it solve the problem?
It restores Visual Studio default settings.
If the problem remains, we can use Visual Studio Setup Wizard (via
Control Panel) to repair Visual Studio. It can restore the Visual
Studio Installation into its original state.
The forum thread is here.
I will provide my results if I make progress.
Using Ctrl + M should toggle this if you're focused on the file having trouble. I had the same problem until I realized had been accidentally using the hot keys to turn this on and off.
Does any else have a problem where when using VS2005 or VS2008, it suddenly 'forgets' to color code and format the text for you? All of a sudden it acts like its a plain old notepad editor. Sometimes if I save and re-open the file, or else re-start Visual studio altogether, it suddenly 'remembers'. I thought maybe this was because of a bad install on my machine, but recently upgraded to a new one, brand new fresh install with all service packs - and we are right back to the erratic behaviour....
Is this a known problem? Is there a workaround (i.e. a key combo I can hit to tell it to do its thing?)
PS: This happens for me when doing asp.net with VB code - not sure if it affects other flavors of the tool...
EDIT: This is a clean install of VS2008 on Vista, but also have had it on XP. No addins on either setup, problem happens routinely.
Sometimes something similar to this happens to me in VB.Net. In my case it has alway been the backgroundcompiler service that has stopped working for one reason or another. Haven't found anything that helps besides restarting visual studio.
I got this often when working on large web projects (> 1K pages and 4K total files) and most often on ashx files.
At the same time, I would lose intellisense, This was happening because the files I was adding were not getting marked as "Compile" in the file properties -> build option.
I never found the cause (assumed it was overburdening the solution) but I found that it would stay fixed for longer if I deleted the SUO file periodically (it was getting into the 1MB range).
Since coming to a new company, new PC, etc, I have not had this problem but then again I'm not working on as large of a web project.
I use C# in VS2008, and haven't had any problems. Maybe this is VB.NET related?
I used to see the problem with "Web Sites". I have since changed most of my projects to "Web Applications" and haven't seen the issue in a while.
I had a similar issue with VS 2003. I use VS 2008 right now and this doesn't happen anymore.