All kinds of weird problems solved just by editing VS shortcut!!

Tech-Archive recommends: Fix windows errors by optimizing your registry

I have just spent the past day and a half trying to fix VS.Net 2003 and
I've finally solved it but I don't have any idea how or why it happened
in the first place!

I'd been developing an ASP.Net solution, everything was working fine
and I had made no changes to my machine when, suddenly, I was no longer
able to build the solution - the error I was getting was "Could not
instantiate the resource processor" - it was having problems with my
resx files (like global.asax.resx).

All the postings I found concerning this error (and the VS Help file)
pointed to this being a corrupted installation and reccommended that I
reinstall Visual Studio. I ended up trying the following: -

Repaired VS.Net
Uninstalled & reinstalled VS.Net
Repaired the .Net framework
Uninstalled & reinstalled the .Net framework
Uninstalled & reinstalled both the framework and VS.Net

None of the above worked!

I had also noticed that all the controls in the webforms toolbox were
greyed-out and so I decided to open a windows application to see if the
windows forms controls were also unavailable only to find that I
couldn't open a form in design-view without getting another error -
this time it was "Required Permissions cannot be acquired".

A google-groups search on this problem led me to the following link: -

http://groups-beta.google.com/group/microsoft.public.vstudio.general/browse_thread/thread/a9e26e005c9df4b4/482abc3d82f0de27

....which details similar syptoms and pointed me to the problem which
was that the shortcut I was using to launch VS had somehow been changed
to a UNC path - in other words, instead of: -

"c:\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\devenv.exe"

....it was...

"\\my_machine_name\c$\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\devenv.exe"

I don't know how it got changed (that's worrying!) but setting it back
to a local path fixed all my problems.

Just thought I'd share that!

Ian

.

Relevant Pages

  • Re: Just your opinion about MFC and C++.NET
    ... > .NET Framework? ... With Visual Studio .NET 2003, we got an additional technology for developing ... Windows applications with C++, .NET Windows Forms which uses the .NET ... Framework classes in place of the MFC classes. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Hobby .NET programming: C++ or C#?
    ... been looking into the Visual Studio Express Editions for C++ and C#. ... .Net Framework or it can use the .Net Framework. ... My motivation for this-- and do correct me if I'm misguided-- is that .NET provides Windows Forms which I understand is a easy way to hook into the Windows GUI facilities. ... My trade off is whether to learn a new language or deal with the increased overhead of making C++ work with .NET. ...
    (comp.programming)
  • Re: .NET Framework 3.5 SP1 install problem ---- Please Help
    ... removed Visual Studio 2008 and reinstalled it. ... Still could not load .NET .SP1 ... Got the following error in the event viewer log (Windows logs,Setup):- ... by using NET Framework Cleanup Tool by Aaron Stebner 'Aaron Stebner's ...
    (microsoft.public.windows.vista.installation_setup)
  • Re: .NET Framework 1.0 WIndows XP Tablet PC
    ... > all the windows XP Tablet PC? ... > prepare a setup to reinstall. ... > Control Panel Add/remove Windows components don't show .NET Framework. ...
    (microsoft.public.dotnet.framework.setup)
  • .NET Framework 1.0 WIndows XP Tablet PC
    ... How can I repair .NET Framework 1.0 WITHOUT reinstall ... all the windows XP Tablet PC? ... Control Panel Add/remove Windows components don't show .NET Framework. ...
    (microsoft.public.dotnet.framework.setup)