I have been working with an Umbraco 4.9 web site. I have been running C# code for it and compiling it through Visual Studio, then I was able to test it by using "Attach to Process" -> w3wp.exe.
Until I made the grave mistake of installing an Extension for VS called ".NET Reflector", because I wanted to try it for another project in VS. Then I came back to developing on the site. I compiled my code for the site only once with that extention installed in VS... then I started having this error every time I tried to "Attach to Process":
System.NullReferenceException occurred
Message=Object reference not set to an instance of an object.
The site works fine with the code I build, but I have no way of testing any of the C# functionality right now because of this Attach to Process problem... I already tried : Uninstalling the extension, deleting all remaining files in extention dir, restarting PC, restarting IIS and I have been digging through all sorts of .config files and through the Internet, but nothing helped so far.
Any suggestions would be welcome, I already spent a day on this issue and I have deadlines at work that I am already behind with. I am the only IT guy in the company so there is no colleague that could help.
PS. I don't understand how one extension could cause such a mess...
I tried installing the extension again, and I just realized there were 4 options in .NET Reflector that were turned on, by default, when I compiled my project.
Those 4 options were :
1. GotoDefinition (F12)
2. Track Loaded Modules
3. Disable Just My Code on startup
4. Decompile from Call Stack
I am assuming one or more of these options possibly changed one or more configuration files of Visual Studio or .NET. I am running out of ideas here, will try to reinstall VS if I don't solve this issue today.
Visual Studio debugging broken by extension
Hello everyone,
I have been working with an Umbraco 4.9 web site. I have been running C# code for it and compiling it through Visual Studio, then I was able to test it by using "Attach to Process" -> w3wp.exe.
Until I made the grave mistake of installing an Extension for VS called ".NET Reflector", because I wanted to try it for another project in VS. Then I came back to developing on the site. I compiled my code for the site only once with that extention installed in VS... then I started having this error every time I tried to "Attach to Process":
Call stack:
The site works fine with the code I build, but I have no way of testing any of the C# functionality right now because of this Attach to Process problem...
I already tried : Uninstalling the extension, deleting all remaining files in extention dir, restarting PC, restarting IIS and I have been digging through all sorts of .config files and through the Internet, but nothing helped so far.
Any suggestions would be welcome, I already spent a day on this issue and I have deadlines at work that I am already behind with. I am the only IT guy in the company so there is no colleague that could help.
PS. I don't understand how one extension could cause such a mess...
I tried installing the extension again, and I just realized there were 4 options in .NET Reflector that were turned on, by default, when I compiled my project.
Those 4 options were :
1. GotoDefinition (F12)
2. Track Loaded Modules
3. Disable Just My Code on startup
4. Decompile from Call Stack
I am assuming one or more of these options possibly changed one or more configuration files of Visual Studio or .NET. I am running out of ideas here, will try to reinstall VS if I don't solve this issue today.
Apparently the problem was:
3.Disable Just My Code on startup.
I enabled Just My Code it in the options again and debugging seems to work fine again, though it is not always hitting breakpoints.
is working on a reply...