.NET still a problem - need better understanding

  • Thread starter Thread starter Robert Schuldenfrei
  • Start date Start date
R

Robert Schuldenfrei

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
 
Robert Schuldenfrei said:
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
Click to expand...

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
 
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
 
Hi Mike & NG,

That will be my last resort. Loading VS 2005 was to be my last step in a
new Vista "clean" install. I would rather not go through that again, but I
will if I have to. Grabbing the wrong disks has certainly taught me a
lesson. Since parts of Beta may be still be around I may have trouble
removing VS 2005, the released version. My third step, after I have a good
understanding of what is and is not on my system, will be to remove VS 2005.

The FIRST STEP is to learn how to use tools to "see" what is there. This is
why I have asked about some program(s) to view how much of what versions of
..NET Framework are actually in play.

Step 2 will be to reinstall OneCare and see if I still get the CLR error
indicating that I still have a faulty Framework installed. If I do, I will
uninstall it again. I have a valid subscription to Norton 360 that I can
use and it may not be bothered by a faulty CLR component.

Step 3 will be a detailed removal of VS 2005. Here is where I really need
to know about the Framework because bits and pieces of it can cause grief
down the road.

Step 4 will be to rebuild the latest release of .NET Framework (3.5) along
with all of the earlier versions that are necessary to end up with fully
functional Framework.

Step 5 will be to install VS 2005 completely and verify that it is running
100% correctly. This, of course, is why I need to learn (and for a 65 year
old, that is not easy. Life was simple when all you had was IBSYS and
FORTRAN:) ) how to use the tools to check the health of the various
components on which Windows depends.

Thanks for your help,

Cheers,

Bob
 
Hello,

I am making progress understanding the problem. I have been looking at the
directory structure \Windows\Microsoft.NET\Framework. I think I know what
is wrong with .NET. Since 2.0 depends on 1.x being there, my system has
almost nothing in the v1.0.3705 and v1.1.4322 folders. I also have that bad
v2.0.50215 folder that is almost empty. My removal attempts probably killed
1.x. I am going to continue to learn about .NET Framework, but my focus
later on this week will be to remove ALL of the .NET Frameworks.

Cheers,

Bob
 
Hi Mike,

That is my position of LAST resort. Aaron Stebner is giving me a hand at
understanding my .NET Framework installation. Rest assured that the Beta VS
2005 hit the trash can as soon as I had realized what I had done. I have
other machines I can use if I need .NET Framework, so I am taking this
opportunity to learn more about .NET and the possibility of a repair. Thank
you for your comments and help.

Cheers,

Bob
 
Dear NG,

This is the final wrap on this issue. In spite of some excellent help from
Microsoft, this problem was never solved. I, and Aaron Stebner, believe
that the issue is lodged deep in the Registry. No amount of reinstallation
of Vista can fix the problem. As a result, I did a clean install of Vista.
Of course, that fixed the problem. Aaron says he is continuing to work the
issue so in the future a repair tool can be fashioned. He has a copy of the
section of my Registry where he believes the trouble is located. I,
however, have moved on. Thank you NG for all of your help and suggestions.

Cheers,

Bob
 
Back
Top