VSNet
-
I learned an important fact about VSNet today... If you delete its HKLM registry keys, it doesn't work. I have written an add-in in VSNet 2002, and was tweaking the installer to install the keys for 2003. Never noticed that I had inadvertantly flagged msiexec to delete the keys on uninstall, INCLUDING the VS keys! Whoops. Gave me the impetus to upgrade though, 2003 installing as I speak. What a nice way to end the holiday weekend. if(E_NOINTERFACE == pThat->QueryInterface(IID_IUnknown,(void**)&pUnk)) { // I aint no pUnk bitch! }
-
I learned an important fact about VSNet today... If you delete its HKLM registry keys, it doesn't work. I have written an add-in in VSNet 2002, and was tweaking the installer to install the keys for 2003. Never noticed that I had inadvertantly flagged msiexec to delete the keys on uninstall, INCLUDING the VS keys! Whoops. Gave me the impetus to upgrade though, 2003 installing as I speak. What a nice way to end the holiday weekend. if(E_NOINTERFACE == pThat->QueryInterface(IID_IUnknown,(void**)&pUnk)) { // I aint no pUnk bitch! }
Steve Hopkins wrote: If you delete its HKLM registry keys, it doesn't work. If you delete its files, it stops working too :laugh: :laugh: My latest article: GBVB - Converting VB.NET code to C#
-
Steve Hopkins wrote: If you delete its HKLM registry keys, it doesn't work. If you delete its files, it stops working too :laugh: :laugh: My latest article: GBVB - Converting VB.NET code to C#
Daniel Turini wrote: If you delete its files, it stops working too Cool, I'll give that a go next. ;P if(E_NOINTERFACE == pThat->QueryInterface(IID_IUnknown,(void**)&pUnk)) { // I aint no pUnk bitch! }
-
I learned an important fact about VSNet today... If you delete its HKLM registry keys, it doesn't work. I have written an add-in in VSNet 2002, and was tweaking the installer to install the keys for 2003. Never noticed that I had inadvertantly flagged msiexec to delete the keys on uninstall, INCLUDING the VS keys! Whoops. Gave me the impetus to upgrade though, 2003 installing as I speak. What a nice way to end the holiday weekend. if(E_NOINTERFACE == pThat->QueryInterface(IID_IUnknown,(void**)&pUnk)) { // I aint no pUnk bitch! }
Steve Hopkins wrote: If you delete its HKLM registry keys, it doesn't work. Same thing with Windows; must be a design flaw. :suss: (*Falcon).Jeremy.GetLatestArticle() = "Learning Binary and Hexadecimal"
-
Daniel Turini wrote: If you delete its files, it stops working too Cool, I'll give that a go next. ;P if(E_NOINTERFACE == pThat->QueryInterface(IID_IUnknown,(void**)&pUnk)) { // I aint no pUnk bitch! }
Steve Hopkins wrote: Cool, I'll give that a go next. Another fun thing to try is what I did on my machine: Install VS.NET 2002. Install VS.NET 2003. Yes! They can run side-by-side. Good. Use VS.NET 2003 for a week until you are sure all your 285 projects are running fine. Uninstall VS.NET 2002, since you do not need it anymore. Lose all your VS file associations and icons. My latest article: GBVB - Converting VB.NET code to C#
-
I learned an important fact about VSNet today... If you delete its HKLM registry keys, it doesn't work. I have written an add-in in VSNet 2002, and was tweaking the installer to install the keys for 2003. Never noticed that I had inadvertantly flagged msiexec to delete the keys on uninstall, INCLUDING the VS keys! Whoops. Gave me the impetus to upgrade though, 2003 installing as I speak. What a nice way to end the holiday weekend. if(E_NOINTERFACE == pThat->QueryInterface(IID_IUnknown,(void**)&pUnk)) { // I aint no pUnk bitch! }
Fix is easy just use repair from add/remove programs. Meg Rules
-
Fix is easy just use repair from add/remove programs. Meg Rules
Unless you delete the installer keys! :laugh:
David Wulff
All goods worth price charged
-
Steve Hopkins wrote: Cool, I'll give that a go next. Another fun thing to try is what I did on my machine: Install VS.NET 2002. Install VS.NET 2003. Yes! They can run side-by-side. Good. Use VS.NET 2003 for a week until you are sure all your 285 projects are running fine. Uninstall VS.NET 2002, since you do not need it anymore. Lose all your VS file associations and icons. My latest article: GBVB - Converting VB.NET code to C#
Daniel Turini wrote: Install VS.NET 2002. Install VS.NET 2003. Yes! They can run side-by-side. Good. Yes but VS.NET 2003 keeps insisting that documentation for it hasn't been installed, though I have MSDN installed-reinstalled-repaired-uninstalled-installed (ack!) several (thousand) times. I don't know if it's because of VS.NET 2002 or something else, but that's meant to drive one crazy for sure. Btw. I have MSDN Jan 2003, should you have any idea why...
-
Daniel Turini wrote: Install VS.NET 2002. Install VS.NET 2003. Yes! They can run side-by-side. Good. Yes but VS.NET 2003 keeps insisting that documentation for it hasn't been installed, though I have MSDN installed-reinstalled-repaired-uninstalled-installed (ack!) several (thousand) times. I don't know if it's because of VS.NET 2002 or something else, but that's meant to drive one crazy for sure. Btw. I have MSDN Jan 2003, should you have any idea why...
Baris Kurtlutepe wrote: Btw. I have MSDN Jan 2003, should you have any idea why... That's the problem. VS.NET 2003 needs MSDN Apr 2003. My latest article: GBVB - Converting VB.NET code to C#