Re: .NET still a problem - need better understanding

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

Hi PVDG42 and NG,

That may be a part of my problem, but the Beta version never got fully installed. That may be a large part of my trouble with the real VS 2005. BUT, I need a better understanding of the .NET Framework before I even try to fix VS. I can take my time with this to gain a deeper understanding of the problem.

SO... I ask again: Does anyone know of a tool (or tools) where I can see what version of .NET Framework is actually on my machine and its health?

If I look in C:\Windows\Microsoft.NET\Framework I see 5 folders:
v1.0.3705
v1.1.4322
v2.0.50215 - This one is fairly empty.
v2.0.50727
VJSharp



"PvdG42" <pvdg@xxxxxxxxxxxxx> wrote in message news:usAkgJfvIHA.524@xxxxxxxxxxxxxxxxxxxxxxx
"Robert Schuldenfrei" <bob@xxxxxxxxxxx> wrote in message news:879ADCBC-BF6C-4334-ADF0-0A28DB8BD561@xxxxxxxxxxxxxxxx
Hi NG,

I have spent the last two days downloading, installing, and trying to view the results. As my other post indicates, I loaded an old Beta of VS 2005. I have since loaded the correct live version, but it has problems. OneCare does not work and issues a CLR error: 80004005. For the moment, I have removed OneCare. I have tried Arron Stebner's suggestion of running sfc /update and it reports no integrity violations. I have tried loading 2.0 and 3.0. The good version of VS seems to have loaded .NET Compact Framework 1.0 SP3 and 2.0 as reported by Vista's Programs and Features.

It is time to take a step back. Does anyone know of a tool that will report exactly what version of .NET Framework is running and some indication of its general health?

TIA,

Bob

When you removed the beta, did you follow the *full manual* procedure for removing all components before installing the version you have now?
VS betas were notorious for causing install and operational issues in later VS installs if the full procedure was not followed.

http://support.microsoft.com/kb/908452

Note Para 1.2


.

Relevant Pages

  • Re: 12 hour update!
    ... The .NET Framework would /NOT/ be offered as an update via Automatic Updates, ... (I've already run the MSRT installation. ... >> any issues installing the MSRT on my own system. ... > mostly because they had installed a Beta version some time in the past. ...
    (microsoft.public.windowsupdate)
  • Re: .NET still a problem - need better understanding
    ... Unfortunately if you didn't fully deinstall the VS 2005 beta, your best tool for cleaning up your system is to reformat your system disk. ... v2.0.50215 - Net Framework 2.0 beta ... I have spent the last two days downloading, installing, and trying to view the results. ...
    (microsoft.public.dotnet.framework)
  • Re: Sharing Executable Applications
    ... Also note that they should have a non beta version of the .Net framework ... deinstalling the beta version and installing the release version of the ... executables. ...
    (microsoft.public.dotnet.languages.vb)
  • RE: Beta 2007 Software
    ... Is it normal to receive an automatic prompt for installing the beta ... Patrick Schmid [OneNote MVP] ... .Will these files cause a problem when trying to reinstall 2007? ...
    (microsoft.public.office.developer.vba)
  • Re: Can Word 2003 & 2007 B2TR retrogressed?
    ... yes I should have said under Beta 2 I had no problems with Office 2003 and ... I presume you are talking about Beta 2 and then installing B2TR? ... Patrick Schmid [OneNote MVP] ... I can then shutdown and restart Word 2003 multiple times and it will ...
    (microsoft.public.office.misc)