[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework

.NET still a problem - need better understanding

Robert Schuldenfrei

5/24/2008 11:49:00 AM

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

8 Answers

PvdG42

5/24/2008 11:03:00 PM

0

"Robert Schuldenfrei" <bob@s-i-inc.com> wrote in message
news:879ADCBC-BF6C-4334-ADF0-0A28DB8BD561@microsoft.com...
> 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...

Note Para 1.2

Robert Schuldenfrei

5/25/2008 11:03:00 PM

0

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@toadstool.edu> wrote in message
news:usAkgJfvIHA.524@TK2MSFTNGP05.phx.gbl...
> "Robert Schuldenfrei" <bob@s-i-inc.com> wrote in message
> news:879ADCBC-BF6C-4334-ADF0-0A28DB8BD561@microsoft.com...
>> 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...
>
> Note Para 1.2
>

Michael D. Ober

5/26/2008 12:38:00 PM

0

Robert,

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. I had the beta
on two different PCs and even with the instructions from MS I had to
reformat both. As for the folders you see

v1.0.3705 - Net Framework 1.0 (unless you have a program that won't run
with 1.1, don't reinstall this one, although v1.1 appears to recreate this
directory)
v1.1.4322 - Net Framework 1.1
v2.0.50215 - Net Framework 2.0 beta
v2.0.50727 - Net Framework 2.0 RTM
VJSharp - Visual J# runtime from Framework 2.0

Mike.


"Robert Schuldenfrei" <bob@s-i-inc.com> wrote in message
news:EC79165A-2775-4C4E-930E-112627382920@microsoft.com...
> 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@toadstool.edu> wrote in message
> news:usAkgJfvIHA.524@TK2MSFTNGP05.phx.gbl...
>> "Robert Schuldenfrei" <bob@s-i-inc.com> wrote in message
>> news:879ADCBC-BF6C-4334-ADF0-0A28DB8BD561@microsoft.com...
>>> 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...
>>
>> Note Para 1.2
>>
>
>

Robert Schuldenfrei

5/26/2008 5:27:00 PM

0

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


"Michael D. Ober" <obermd.@.alum.mit.edu.nospam.> wrote in message
news:T5GdnWa_cLqPMqfVnZ2dnUVZ_q3inZ2d@earthlink.com...
> Robert,
>
> 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. I had
> the beta on two different PCs and even with the instructions from MS I had
> to reformat both. As for the folders you see
>
> v1.0.3705 - Net Framework 1.0 (unless you have a program that won't run
> with 1.1, don't reinstall this one, although v1.1 appears to recreate this
> directory)
> v1.1.4322 - Net Framework 1.1
> v2.0.50215 - Net Framework 2.0 beta
> v2.0.50727 - Net Framework 2.0 RTM
> VJSharp - Visual J# runtime from Framework 2.0
>
> Mike.

Robert Schuldenfrei

5/28/2008 3:19:00 PM

0

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


"Robert Schuldenfrei" <bob@s-i-inc.com> wrote in message
news:879ADCBC-BF6C-4334-ADF0-0A28DB8BD561@microsoft.com...
> 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

Michael D. Ober

5/28/2008 11:44:00 PM

0

Net 2.0 doesn't require or use any of the NET 1.x files. Net versions after
2.0 do install and use the 2.0 framework and runtime. It appears that NET
1.1 does use some of the NET 1.0 files. Your problem is that you installed
the 2.0 Beta and haven't completely removed it. The best way of removing it
is to throw away the NET 2.0 beta CD/DVDs, backup your system, and reinstall
the OS starting with a Format. Then reinstall the NET framework 3.5
(download it from MS). You will discover that there are no NET 1.x
directories.

Mike.

"Robert Schuldenfrei" <bob@s-i-inc.com> wrote in message
news:6F6625F0-DB77-4428-BB21-436521AA697F@microsoft.com...
> 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
>
>
> "Robert Schuldenfrei" <bob@s-i-inc.com> wrote in message
> news:879ADCBC-BF6C-4334-ADF0-0A28DB8BD561@microsoft.com...
>> 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

5/29/2008 1:06:00 PM

0

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

"Michael D. Ober" <obermd.@.alum.mit.edu.nospam.> wrote in message
news:I-adnX5t3-DEc6DVnZ2dnUVZ_qDinZ2d@earthlink.com...
> Net 2.0 doesn't require or use any of the NET 1.x files. Net versions
> after 2.0 do install and use the 2.0 framework and runtime. It appears
> that NET 1.1 does use some of the NET 1.0 files. Your problem is that you
> installed the 2.0 Beta and haven't completely removed it. The best way of
> removing it is to throw away the NET 2.0 beta CD/DVDs, backup your system,
> and reinstall the OS starting with a Format. Then reinstall the NET
> framework 3.5 (download it from MS). You will discover that there are no
> NET 1.x directories.
>
> Mike.
>
> "Robert Schuldenfrei" <bob@s-i-inc.com> wrote in message
> news:6F6625F0-DB77-4428-BB21-436521AA697F@microsoft.com...
>> 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
>>
>>
>> "Robert Schuldenfrei" <bob@s-i-inc.com> wrote in message
>> news:879ADCBC-BF6C-4334-ADF0-0A28DB8BD561@microsoft.com...
>>> 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

6/4/2008 8:38:00 PM

0

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


"Robert Schuldenfrei" <bob@s-i-inc.com> wrote in message
news:879ADCBC-BF6C-4334-ADF0-0A28DB8BD561@microsoft.com...
> 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