dot net framework - something missing

[StoneCherub]

Please move this if it's in the wrong place.

My add/remove shows that I have all the pieces of the dot net framework
thru 3.5 with patches. But neither VWDexpress nor Ironspeed developer will
work because my windows\assembly folder is empty and both application
failures report a need for dll files that are supposed to be in what appears
to be a complex structure in that folder.

How can I fix this?

[Unknown]

Try uninstalling and then reinstalling.
Note the best of answers I know but it's
worth a try.

--
JS
http://www.pagestart.com

"StoneCherub" <Stone...@discussions.microsoft.com> wrote in message
news:2F9FD688-3BA9-445D...@microsoft.com...

[StoneCherub]

That was my first thought but I was hoping there might be a easier way.

If you want to do work, get a MAC. If you want to play with the computer
there's Microsoft.

Dan

[PA Bear [MS MVP]]

[Crosspost to DotNet Framework newsgroup]

Please state your full Windows version (e.g., WinXP SP3) when posting to
this newsgroup.

1. Before doing anything else, write down the .NET Framework versions which
are already installed:

How to determine which versions of the .NET Framework are installed and
whether service packs have been applied
http://support.microsoft.com/kb/318785

2. Now see Resolution Method 2 in http://support.microsoft.com/kb/923100
(ignore the title). After running the appropriate/needed tool, (re)install
all .NET Framework versions manually using the download links on the page.
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002

[Paul]

There is a blog here, from someone who works on .NET . There is apparently
an option to repair a .NET installation. And this person has also written
a verifier tool of some sort.

http://blogs.msdn.com/astebner/pages/unified-net-framework-troubleshooting-guide.aspx

Paul

[Unknown]

First determine which versions of .NET Framework are installed and
whether any service packs have been applied:
See: http://support.microsoft.com/kb/318785

Next download to your hard drive each version of NET
you have on your PC. download the installation files
(do not use Windows Update) from this list
"Where to download the .Net Redistributables"
http://www.pagestart.com/netframeworkdwnldlinks.html

Then uninstall each version .NET you have on your PC,
Starting with the highest version first and finally uninstalling NET 1.x
(Remove 1.1 hotfix after removing .Net 1.1) if its on your PC.

Now use the .Net Cleanup Tool to
remove the last vestiges of .Net

.NET Framework Cleanup Tool:
http://blogs.msdn.com/astebner/pages/8904493.aspx
"This .NET Framework cleanup tool is designed to automatically perform a set
of steps to remove selected versions of the .NET Framework from a computer,
It will remove files, directories, registry keys and values and Windows
Installer product registration information for the .NET Framework.
The tool is intended primarily to return your system to a known
(relatively clean) state in case you are encountering .NET Framework
installation, uninstallation, repair or patching errors so that you can try
to install
again". I used this tool after using the Add or Remove Programs uninstall
feature. After using the Cleanup tool only a few folders and files still
remained, so I deleted these manually (See below)

.Net folders - After deleting all .Net Redistributables:
C:\Program Files\Reference Assemblies\
(Delete the Reference Assemblies folder and all subfolders )
C:\WINDOWS\assembly
(Delete the assembly folder and all subfolders)
C:\WINDOWS\Microsoft.NET\Framework
(Delete the Microsoft .Net folder and all subfolders)
C:\Program Files\MSBuild\Microsoft\Windows Workflow Foundation\
(May or May not exist)

Next reinstall each version you had on your computer
working your way back up to the last (highest version #) of NET.

NET Framework Setup Verification Tool:
http://blogs.msdn.com/astebner/pages/8999004.aspx
"This .NET Framework setup verification tool is designed to automatically
perform a set of steps to verify the installation state of one or more
versions of the .NET Framework on a computer."

Then check for any .net security updates/hotfixes using Windows Update.

--
JS
http://www.pagestart.com

"StoneCherub" <Stone...@discussions.microsoft.com> wrote in message

news:391CA74C-B44C-4F05...@microsoft.com...

[StoneCherub]

This is messier and messier. I had to rebuild my last install of XP, it
rotted as do they all, and was apparently careless in the install of dot net
framework. I found all the folders listed in the kb article but when I opened
1.0 it had mscommc.dll and three config files. 1.1 had two config files. 2.0
seemed to have a file structure, nine directories and 200 files. 3.0 had two
foundation folders and wpf. 3.5 had six folders and three dozen files.

This is a whole mess. It looks like 1.0 and 1.1 aren't there, 2.0 is and
3.0and 3.5 may or may not be, I have no way of knowing.

Can I apply one of the removal programs to scrub the whole mess and just
start over? I don't want to rebuild again.

Dan Lynch

"JS" wrote:

> First determine which versions of .NET Framework are installed and
> whether any service packs have been applied:
> See: http://support.microsoft.com/kb/318785
>
> Next download to your hard drive each version of NET
> you have on your PC. download the installation files
> (do not use Windows Update) from this list
> "Where to download the .Net Redistributables"
> http://www.pagestart.com/netframeworkdwnldlinks.html
>
> Then uninstall each version .NET you have on your PC,
> Starting with the highest version first and finally uninstalling NET 1.x
> (Remove 1.1 hotfix after removing .Net 1.1) if its on your PC.
>
> Now use the .Net Cleanup Tool to
> remove the last vestiges of .Net
>

> ..NET Framework Cleanup Tool:

> http://blogs.msdn.com/astebner/pages/8904493.aspx
> "This .NET Framework cleanup tool is designed to automatically perform a set
> of steps to remove selected versions of the .NET Framework from a computer,
> It will remove files, directories, registry keys and values and Windows
> Installer product registration information for the .NET Framework.
> The tool is intended primarily to return your system to a known
> (relatively clean) state in case you are encountering .NET Framework
> installation, uninstallation, repair or patching errors so that you can try
> to install
> again". I used this tool after using the Add or Remove Programs uninstall
> feature. After using the Cleanup tool only a few folders and files still
> remained, so I deleted these manually (See below)
>

> ..Net folders - After deleting all .Net Redistributables:

[Unknown]

The verification program I mentioned
in my earlier post will tell you which
versions are still valid.

I should have mentioned that even the
removal tool will not remove every last
file or folder but it does remove far more
than what left behind after using the Add/Remove
option (which is what you want to start with and
then use the removal tool)

For more info you can read the .NET articles
I've put on my web site: http://www.pagestart.com/windowsxptips.html

--
JS
http://www.pagestart.com

"StoneCherub" <Stone...@discussions.microsoft.com> wrote in message

news:6494B858-7B81-415C...@microsoft.com...

[PA Bear [MS MVP]]

See my first reply to your post:
http://groups.google.com/group/microsoft.public.windowsxp.general/msg/e930c33fa41025b2

[StoneCherub]

RESOLUTION - or not.

I sifted through the various Kb articles which were, alas, mostly useless to
me. The best was Where to download the .Net redistributables - which I did.

With all the exe's available and the framework "removed," I started with 1.0
which loaded OK. But, when I started the SP2 exe for this install, I was
informed that the file I was using was not on my computer. Applying SP1
against recommendations did not remove this roadblock. Neither did using
another download of the same file. SP3 loaded OK but, with the faulty
foundation, I could not build a new framework.

I have wasted enough time with this. XP is getting old, like me, and I have
been toying with a transition to Windows 7 based on recommendations from
another forum.

Thanks, all, for your help.

[PA Bear [MS MVP]]

Backup your personal data, then do a format & clean install of Windows.
Please note that a Repair Install (AKA in-place upgrade) will NOT fix this!

cf. http://michaelstevenstech.com/cleanxpinstall.html#steps

After the clean install, you'll have the equivalent of a "new computer" so
take care of everything on the following page before otherwise connecting
the machine to the internet or a network and before using a USB key that
isn't brand-new or hasn't been freshly formatted:

5 steps to help protect your new computer before you go online
http://www.microsoft.com/protect/computer/advanced/xppc.mspx

HOW TO get a computer running WinXP Gold (no Service Packs) fully patched
(after a clean install)
http://groups.google.com/group/microsoft.public.windowsupdate/msg/3f5afa8ed33e121c

HOW TO get a computer running WinXP SP1(a) or SP2 fully patched (after a
clean install)
http://groups.google.com/group/microsoft.public.windowsxp.general/msg/a066ae41add7dd2b

Also see:

Steps To Help Prevent Spyware
http://www.microsoft.com/protect/computer/spyware/prevent.mspx

Rogue Security Software - Microsoft Security:
http://www.microsoft.com/protect/computer/viruses/rogue.mspx

[StoneCherub]

That is the black hole into which I have been staring since this problem
began. Had I done it last week, I would be working now rather than writing
this. A complete rebuild would have taken less time.

Facing a rebuild of an old OS while I have been contemplating moving on to
Windows 7, I have decided to get Vista anticipating a move to W7 when it
ships. As an actual conservative, I have never installed a new MS OS before
and this will be my first experience with Vista, it's old enough.

Thanks for the help.