Installation of dotnetfx.exe - .net framework

[George]

I have VB.Net Standard 2003 on Windows XP Home Edition.
Ready to deploy first application.
I downloaded dotnetfx.exe today; it's File version 1.1.4322.573.

When the client manually starts dotnetfx.exe, what happens?
The first message is "Would you like to install Microsft.NET Framework
1.1 Package?"

To provide some guidance to clients, I'd like to know the remaining
questions. But I'm concerned about doing this on my own PC. Is it safe
to do this, placing the new framework stuff in a different folder?

What folders/directories are created? Does it matter where these are
located, what names are assigned etc.?

Are the files created by dotnetfx.exe exactly the same as whatever I
already have as a part of VB.net?

Thanks,
George

 

[Sueffel]

There's no options, they just basically hit okay/next and it installs the 30
someodd MB into the %SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322 folder,
that's standard. Or, if you don'tmind making a 30MB installer, include the
redist in your app's setup, then your installer will take care of that
tedious work for you

Happy hunting,
Sueffel

 

[George]

Thanks Sueffel,

As mentioned, I have vb.net 2003, ordered in October 2003, received
early November.

A search for "Framework" shows two main folders:
C:\Windows\Microsoft.NET\Framework\v1.0.3705 (33mb) created May
16,2002
C:\Windows\Microsoft.NET\Framework\v1.1.4322 (55mb) created July
6,2003

I don't know where v1.0.3705 came from; can I just delete that folder?

I just discovered that the first CD "Prerequisites" in my vb.net 2003
package includes folder dotNetFramework which has one file:
dotnetfx.exe, with file version 1.1.4322.573, creation date Feb
21,2003.

It appears that the file (1.1.4322.573) has not changed in the last
year.

I wonder why the installation of vb.net did not copy this to my PC?

Why does my Framework\v1.1.4322 show a creation date of July 6,2003?
It appears that it may have been created as a separate function in the
instalation process rather than an automatic execution of dotnetfx.exe
on the CD. Otherwise, wouldn't it have a creation date of Feb 21,2003?

I had done a search for this file dotnetfx.exe yesterday, with 0 files
found.
So I downloaded the file; it shows as file version 1.1.4322.573,
creation date March 29,2004.

If I run this dotnetfx.exe, will a new folder be created:
C:\Windows\Microsoft.NET\Framework\v1.1.4322.573 ?

Or will it replace the
existing C:\Windows\Microsoft.NET\Framework\v1.1.4322 ?

Also, notice it is more than "30 someodd MB" most persons mention.

George

 

[Sueffel]

Well, the 1.0 version is there for backwards compatability, and I think that
maybe VS 2k3 installed it, so I wouldn't delete it. As far as the
compatability thing, I have broken it by using GDI calls, so that isn't
backwards compatable.

HTH,
Sueffel

 

[George]

Sueffel,
Please explain "backwards compatability". Do you mean the version 1.0
would support vb.net applications created earlier than version "2003"?

The dotnetfx.exe file I downloaded on 3/29/04; if the mouse hovers
over this file in Windows Explorer, it shows File Version
1.1.4322.573.
My question was "If I run this file what happens?" (see my earlier
post)

My experince follows:
----------------

Message 1 "Would you like to install Microsft.NET Framework 1.1
Package?"
(reply OK)
(installation proceeds with no prompts, as you indicated)
Message 2 ("Installation of Microsoft.NET Framework 1.1 is complete."
(reply OK)

Upon checking Windows Explorer, I got the answer: A new folder
v1.1.4322.573 was Not created. I'm not sure what the dotnetfx.exe
actually does if an existing same-version product is found. Does it
delete the existing folder and re-load all the files?

It does Not remove previous versions of Framework; evidently there is
a reason for this, as you indicated.

The "new" folder has identical properties as the original:
Creation date July 6,2003
Size on disk: 55.4mb
294 files, 15 folders.
The Date Modified detail shows 3/31/2004.

Checking Control Panel, I find both v1.0 and v1.1.

The file size for v1.1 shows 37.7mb, compared with 55.4mb from WE.
Clicking on
"size" here shows a msg "This is just an estimate".

Clicking on Support Info has a readme file. It does not explain
anything about Framework itself but "Installation Repair", a cryptic
command line that repairs the application. Hope I never have to use
it.

George