|
|
You're in the
visual studio .net setup
group:Help - repair and re-installs fail
visual studio .net setup:
I have attempted to repair and re-install VB.Net so many times and variations
now it isn't funny. I had a working installation at one time - and to this day do not know why things chnaged. I have virus scanned, and adware scanned and nothing appears unusual. One day, however, Visual Studio failed to recognize vbprojects and has remained that way to this day. The about box in Vis Studio fails to show VB as an installed language - despite clean boots, cleaning out the temp folders, complete un-installs with subsequent re-installs, and everything else I have tried. I am 2 steps from dumping the product in the circular file (you know what I mean)... too bad I would like to be able to use it. Has anyone experianced similar loss of their language from VisStudio ? and how did you overcome it? Please - constructive suggestions only. --
Product is simply VB.net 2003 Std - OS WinXP
[quoted text, click to view] "Peter van der Goes" wrote:
> > "Joe User" <JoeUser@somewhere.com> wrote in message > news:E0F04929-BC58-4432-BCE3-93F37385B3B8@microsoft.com... > >I have attempted to repair and re-install VB.Net so many times and > >variations > > now it isn't funny. I had a working installation at one time - and to > > this > > day do not know why things chnaged. I have virus scanned, and adware > > scanned > > and nothing appears unusual. One day, however, Visual Studio failed to > > recognize vbprojects and has remained that way to this day. The about box > > in > > Vis Studio fails to show VB as an installed language - despite clean > > boots, > > cleaning out the temp folders, complete un-installs with subsequent > > re-installs, and everything else I have tried. I am 2 steps from dumping > > the > > product in the circular file (you know what I mean)... too bad I would > > like > > to be able to use it. Has anyone experianced similar loss of their > > language > > from VisStudio ? and how did you overcome it? Please - constructive > > suggestions only. > > > > -- > > Joe > It sounds like you are a candidate for the manual uninstall procedures. > After so many reinstall attempts, you need a thorough cleaning. > I'm a little unclear on exactly which product you have. Is it: > > Visual Studio .NET 2002 > Visual Studio .NET 2003 > Visual Basic .NET Standard Edition 2002, or > Visual Basic .NET Standard Edition 2003? > > Regardless, here are links to instructions which may be helpful: > > http://support.microsoft.com/default.aspx?scid=kb;en-us;824642 > http://support.microsoft.com/default.aspx?scid=kb;en-us;315779 > > -- > Peter [MVP Visual Developer] > Jack of all trades, master of none. > >
.... and I tried the key part of the manual methods - deleting the former
installation - and successfully was able to get the installer to think it was a fresh install - requiring the product key all over again. Still - no VB capability within Vis Studio. J [quoted text, click to view] "Peter van der Goes" wrote:
> > "Joe User" <JoeUser@somewhere.com> wrote in message > news:E0F04929-BC58-4432-BCE3-93F37385B3B8@microsoft.com... > >I have attempted to repair and re-install VB.Net so many times and > >variations > > now it isn't funny. I had a working installation at one time - and to > > this > > day do not know why things chnaged. I have virus scanned, and adware > > scanned > > and nothing appears unusual. One day, however, Visual Studio failed to > > recognize vbprojects and has remained that way to this day. The about box > > in > > Vis Studio fails to show VB as an installed language - despite clean > > boots, > > cleaning out the temp folders, complete un-installs with subsequent > > re-installs, and everything else I have tried. I am 2 steps from dumping > > the > > product in the circular file (you know what I mean)... too bad I would > > like > > to be able to use it. Has anyone experianced similar loss of their > > language > > from VisStudio ? and how did you overcome it? Please - constructive > > suggestions only. > > > > -- > > Joe > It sounds like you are a candidate for the manual uninstall procedures. > After so many reinstall attempts, you need a thorough cleaning. > I'm a little unclear on exactly which product you have. Is it: > > Visual Studio .NET 2002 > Visual Studio .NET 2003 > Visual Basic .NET Standard Edition 2002, or > Visual Basic .NET Standard Edition 2003? > > Regardless, here are links to instructions which may be helpful: > > http://support.microsoft.com/default.aspx?scid=kb;en-us;824642 > http://support.microsoft.com/default.aspx?scid=kb;en-us;315779 > > -- > Peter [MVP Visual Developer] > Jack of all trades, master of none. > >
[quoted text, click to view] "Joe User" <JoeUser@somewhere.com> wrote in message It sounds like you are a candidate for the manual uninstall procedures. news:E0F04929-BC58-4432-BCE3-93F37385B3B8@microsoft.com... >I have attempted to repair and re-install VB.Net so many times and >variations > now it isn't funny. I had a working installation at one time - and to > this > day do not know why things chnaged. I have virus scanned, and adware > scanned > and nothing appears unusual. One day, however, Visual Studio failed to > recognize vbprojects and has remained that way to this day. The about box > in > Vis Studio fails to show VB as an installed language - despite clean > boots, > cleaning out the temp folders, complete un-installs with subsequent > re-installs, and everything else I have tried. I am 2 steps from dumping > the > product in the circular file (you know what I mean)... too bad I would > like > to be able to use it. Has anyone experianced similar loss of their > language > from VisStudio ? and how did you overcome it? Please - constructive > suggestions only. > > -- > Joe After so many reinstall attempts, you need a thorough cleaning. I'm a little unclear on exactly which product you have. Is it: Visual Studio .NET 2002 Visual Studio .NET 2003 Visual Basic .NET Standard Edition 2002, or Visual Basic .NET Standard Edition 2003? Regardless, here are links to instructions which may be helpful: http://support.microsoft.com/default.aspx?scid=kb;en-us;824642 http://support.microsoft.com/default.aspx?scid=kb;en-us;315779 -- Peter [MVP Visual Developer] Jack of all trades, master of none.
[quoted text, click to view] "Joe User" <JoeUser@somewhere.com> wrote in message Under those circumstances, I'd be considering using telephone technical news:E71D2BBD-51F7-4B51-A095-B0DF3D3F230D@microsoft.com... > ... and I tried the key part of the manual methods - deleting the former > installation - and successfully was able to get the installer to think it > was > a fresh install - requiring the product key all over again. Still - no VB > capability within Vis Studio. > > J > support. IIRC, all the developer products come with two free support incidents at minimum. (800) 936-5800, I believe. -- Peter [MVP Visual Developer] Jack of all trades, master of none.
For anyone with similar problems: It turns out that this was the way to go
- After multiple trial and errors - we were able to identify the problem as a failure of a damaged .Net Framework. MS Support has a cleanup tool that will wipe the Framework from your system - better than other methods published - and the re-install of the Framework fixed the problems with VS.Net recognizing and acknowledging the installed languages (in this case VB.Net). Note the VS.Net repair of the framework (prerequisits disk) and other methods did NOT work. So, if you are experiancing similar problems note that a) MS Installation support is free (which this qualifies for) and b) ask for the wipe utility for the Framework - from the VS support engineer. JU [quoted text, click to view] "Peter van der Goes" wrote:
> > "Joe User" <JoeUser@somewhere.com> wrote in message > news:E71D2BBD-51F7-4B51-A095-B0DF3D3F230D@microsoft.com... > > ... and I tried the key part of the manual methods - deleting the former > > installation - and successfully was able to get the installer to think it > > was > > a fresh install - requiring the product key all over again. Still - no VB > > capability within Vis Studio. > > > > J > > > Under those circumstances, I'd be considering using telephone technical > support. IIRC, all the developer products come with two free support > incidents at minimum. > > (800) 936-5800, I believe. > > -- > Peter [MVP Visual Developer] > Jack of all trades, master of none. > >
[quoted text, click to view] "Joe User" <JoeUser@somewhere.com> wrote in message Thanks for posting back with the information, Joe! news:D678AFDA-AC56-4332-AA31-823E4D684B35@microsoft.com... > For anyone with similar problems: It turns out that this was the way to > go > - After multiple trial and errors - we were able to identify the problem > as a > failure of a damaged .Net Framework. MS Support has a cleanup tool that > will > wipe the Framework from your system - better than other methods > published - > and the re-install of the Framework fixed the problems with VS.Net > recognizing and acknowledging the installed languages (in this case > VB.Net). > Note the VS.Net repair of the framework (prerequisits disk) and other > methods > did NOT work. So, if you are experiancing similar problems note that a) > MS > Installation support is free (which this qualifies for) and b) ask for the > wipe utility for the Framework - from the VS support engineer. > > JU >
[quoted text, click to view] Joe User wrote: > For anyone with similar problems: It turns out that this was the way to go > - After multiple trial and errors - we were able to identify the problem as a > failure of a damaged .Net Framework. MS Support has a cleanup tool that will > wipe the Framework from your system - better than other methods published - > and the re-install of the Framework fixed the problems with VS.Net > recognizing and acknowledging the installed languages (in this case VB.Net). > Note the VS.Net repair of the framework (prerequisits disk) and other methods > did NOT work. So, if you are experiancing similar problems note that a) MS > Installation support is free (which this qualifies for) and b) ask for the > wipe utility for the Framework - from the VS support engineer. Thanks for that information! "MS Support has a cleanup tool that will wipe the Framework from your system" This looks like just what I need. Where can I find this tool? ...John
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |