VB.Net Application Deployment Wizard

[Guest]

When I use the wizard to add the setup project to my applicaiton, it puts a
file called "dotnetfx.exe" in the Release Directory. However, I find that I
really don't need this file to distribute my application as the .msi and
setup files run quite well without it. What is this file used for. It's
23mb and I don't want to distribute it.

Also, I assume I can just distribute the .msi, setup.exe, config.ini, and
setup.ini files and the installation will work fine on target computers so
long as the have the proper framework...is this correct?

 

[m.posseth]

Dennis

dotnetfx.exe is the frameworks redistributable file ,,, so it is only
necessary for computers wich do not have the framework installed
probably your target audience keeps there computer up to date ( wish mine
were like that to )

by the way on a computer without the framework your setup will just work
fine ( as the installer has its own runtime ennvironment ) however your
proggy will not run


regards

Michel Posseth [MCP]

 

[Guest]

Thanks a lot for your answer. I guess that if a computer did not have the
framework then it would be automatically installed if the dotnetfx file was
included in my distribution package. Is this right?
--
Dennis in Houston

Dennis

dotnetfx.exe is the frameworks redistributable file ,,, so it is only
necessary for computers wich do not have the framework installed
probably your target audience keeps there computer up to date ( wish mine
were like that to )

by the way on a computer without the framework your setup will just work
fine ( as the installer has its own runtime ennvironment ) however your
proggy will not run


regards

Michel Posseth [MCP]

When I use the wizard to add the setup project to my applicaiton, it puts
a
file called "dotnetfx.exe" in the Release Directory. However, I find that
I
really don't need this file to distribute my application as the .msi and
setup files run quite well without it. What is this file used for. It's
23mb and I don't want to distribute it.

Also, I assume I can just distribute the .msi, setup.exe, config.ini, and
setup.ini files and the installation will work fine on target computers so
long as the have the proper framework...is this correct?

 

[m.posseth]

Yes it is

however if you can shift the .Net runtime environment necesarity to the
system administrator this would be a much better choice as the overhead of
25 mb to a application deploy of normally just a few kb`s is pretty high

watch out with fireworks

Hope you have a happy 2006

Michel Posseth [MCP]

Thanks a lot for your answer. I guess that if a computer did not have the
framework then it would be automatically installed if the dotnetfx file
was
included in my distribution package. Is this right?
--
Dennis in Houston

Dennis

dotnetfx.exe is the frameworks redistributable file ,,, so it is only
necessary for computers wich do not have the framework installed
probably your target audience keeps there computer up to date ( wish
mine
were like that to )

by the way on a computer without the framework your setup will just work
fine ( as the installer has its own runtime ennvironment ) however your
proggy will not run


regards

Michel Posseth [MCP]

When I use the wizard to add the setup project to my applicaiton, it
puts
a
file called "dotnetfx.exe" in the Release Directory. However, I find
that
I
really don't need this file to distribute my application as the .msi
and
setup files run quite well without it. What is this file used for.
It's
23mb and I don't want to distribute it.

Also, I assume I can just distribute the .msi, setup.exe, config.ini,
and
setup.ini files and the installation will work fine on target computers
so
long as the have the proper framework...is this correct?

 

[Guest]

Great. What I'll do is present two different downloads, i.e., one with the
framework and one without and the user can decide for himself if he has the
framework 1.1 or later installed. Have a happy new year and hope you got all
you wanted for Xmas.
--
Dennis in Houston

Yes it is

however if you can shift the .Net runtime environment necesarity to the
system administrator this would be a much better choice as the overhead of
25 mb to a application deploy of normally just a few kb`s is pretty high

watch out with fireworks

Hope you have a happy 2006

Michel Posseth [MCP]

Thanks a lot for your answer. I guess that if a computer did not have the
framework then it would be automatically installed if the dotnetfx file
was
included in my distribution package. Is this right?
--
Dennis in Houston

Dennis

dotnetfx.exe is the frameworks redistributable file ,,, so it is only
necessary for computers wich do not have the framework installed
probably your target audience keeps there computer up to date ( wish
mine
were like that to )

by the way on a computer without the framework your setup will just work
fine ( as the installer has its own runtime ennvironment ) however your
proggy will not run


regards

Michel Posseth [MCP]


When I use the wizard to add the setup project to my applicaiton, it
puts
a
file called "dotnetfx.exe" in the Release Directory. However, I find
that
I
really don't need this file to distribute my application as the .msi
and
setup files run quite well without it. What is this file used for.
It's
23mb and I don't want to distribute it.

Also, I assume I can just distribute the .msi, setup.exe, config.ini,
and
setup.ini files and the installation will work fine on target computers
so
long as the have the proper framework...is this correct?