Click here to Skip to main content
15,117,830 members
Please Sign up or sign in to vote.
4.00/5 (1 vote)
See more:

I am trying to install .net 2.0 on XP, but when it finishis unpacking, it does nothing. No errorcode, nothing. Just closes the unpacker window, and stops there. I can't get why. I don't know what else could I write about this problem, so feel free to ask.

1 solution

It is possible that the correct .NET framework is already installed, and the installer has nothing more to do.
You can check quite easily, but you need IE (if definitely doesn't work in Chrome)

Bring up IE and paste into the address bar:
Press ENTER.
You will get a popup saying something along the lines of:
Mozilla/4.0 (compatible; MSIE8.0; Windows NT 5.1; Trident/4.0;
Followed by a number of ".NET CLR" versions. If 2.0 is in there (and it is quite probable) then the installer just didn't need to do anything!
Sergey Alexandrovich Kryukov 28-Apr-11 15:05pm
Ha! What a funny method of detection of the Framework. Like it! My 5.
OriginalGriff 28-Apr-11 15:09pm
Well, you can't write a C# program to do it... :laugh:
Sergey Alexandrovich Kryukov 28-Apr-11 16:02pm
That probably would be exactly my first thought: write an application for each target platform and watch which of the applications would show a spectacular failure. :-)
Rick Shaub 28-Apr-11 15:07pm
Good answer.
velvet7 28-Apr-11 15:09pm
Actually, I haven't think about it already, maybe you are right. I will check it tomorrow (because the computer is far away from me). First when I started my c# application it threw an error, and I thought it was the framework, but then no. Well, tomorrow I check that error code again.
Thanks, question answered.
Manfred Rudolf Bihy 28-Apr-11 15:35pm
That's quite a tip there, have my 5!
OriginalGriff 29-Apr-11 3:08am
Personally, I don't like that you can execute code in the address bar: I think it is a potential security risk. But, if you are on the phone to a custard (a cross between a customer and a b@stard) then this is a simple method that even a pretty non-technical person can cope with!
The only other ways for a user to check are in the registry (and some people should not be allowed near Regedit), or to check for a folder called "%windir%\Microsoft.NET\Framework\" and see what sub-directories exist. Since this means them looking into the Windows directory, I don't like to go there either!
Manfred Rudolf Bihy 29-Apr-11 8:51am
Custard LOL, I'll have to remember that one!

BTW there are people that shouldn't even be let near to anything resembling a computer not to mention letting them fiddle around with the registry of one. :)

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900