Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / VB.NET / December 2005

Tip: Looking for answers? Try searching our database.

VB.Net Application Deployment Wizard

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Dennis - 30 Dec 2005 23:00 GMT
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?
Signature

Dennis in Houston

m.posseth - 31 Dec 2005 09:11 GMT
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
[quoted text clipped - 7 lines]
> setup.ini files and the installation will work fine on target computers so
> long as the have the proper framework...is this correct?
Dennis - 31 Dec 2005 15:03 GMT
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?
Signature

Dennis in Houston

> Dennis
>
[quoted text clipped - 22 lines]
> > 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 - 31 Dec 2005 15:13 GMT
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
[quoted text clipped - 34 lines]
>> > so
>> > long as the have the proper framework...is this correct?
Dennis - 31 Dec 2005 15:27 GMT
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.
Signature

Dennis in Houston

> Yes it is
>
[quoted text clipped - 46 lines]
> >> > so
> >> > long as the have the proper framework...is this correct?

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.