HighTechTalks DotNet Forums  

Re: Installation of dotnetfx.exe - .net framework

VB.net microsoft.public.dotnet.languages.vb


Discuss Re: Installation of dotnetfx.exe - .net framework in the VB.net forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
Sueffel
 
Posts: n/a

Default Re: Installation of dotnetfx.exe - .net framework - 04-02-2004 , 10:27 PM






v 1.0 is for VS 2k2, v 1.1 is for 2k3, and (this is what I've heard) v 2.0
is for Whidby. What I mean by "backward compatabilty" is one version of
something can run an older version. So, that would mean v 1.1 Framework
"should" run a v 1.0 assembly. I've found this is broke with GDI+/Forms.
from what I've seen, VS 2k3 installs both version (v 1.0 and v1.1) for this
reason. Not able to verify that one, but it does make sense considering how
well MS has done with backwards compatability in the past (sorry guys, the
record speaks). Personally, I wouldn't worry a hoot about it, just making
more stress for yourself than you already have.
I have come to an epiphany as of late, how many people use Windows Update?
I'd estimate atleast 90% of the market. Now, how many get ALL the updates
because they are told to? Probably 90% of the 90%. That's not directly
confimable, just a personal observation, people lately like being told what
to do. anyhew, nuf of my ranting. I wouldn'tworry bout it, but if you are,
just tell your setup project to include the framework

Sueffel

"George" <tek1940 (AT) hotmail (DOT) com> wrote

Quote:
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



"Sueffel" <someone (AT) somewhere (DOT) com> wrote

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" <tek1940 (AT) hotmail (DOT) com> wrote in message
news:c1a4a495.0403300936.1bbba59c (AT) posting (DOT) google.com...
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" <someone (AT) somewhere (DOT) com> wrote in message
news:<#eH#tIhFEHA.3424 (AT) tk2msftngp13 (DOT) phx.gbl>...
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" <tek1940 (AT) hotmail (DOT) com> wrote in message
news:c1a4a495.0403291853.5a138d8 (AT) posting (DOT) google.com...
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



Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.