Package and Deployment Wizard

[John G Duffy]

Just created my first VB.NET application and used the Package and Deployment wizard for its intended purpose.
I tried to install the resultant output on a Windows ME system and got ugly message saying the .NET framework is needed on the target system.
Is not the P&D wizard supposed to supply all necessary files? I would hate to have to install Framework on all receiving systems.
The tutorial I am using says P&D should have produced a 15MB file but the .msi file outputted was only 30KB or so.
'
ALSO, during P&D package creation, I got a warning about the package does not contain the .Net framework. (Probably the reason it did not install).
I could not find any options to include or exclude the necessary files from framework. Obviously I am missing something and the turtorial does not go into this. My limited knowledge at this time is apparent.
'
Can any one Help??

'
'
Please rate it if it answers the question
or is useful.
'
John G

[Craig Gemmill]

I as well have very limited knowledge about this issue, seeing as how the new p&d system is a little tricky. The only thing I can think of is to make sure you are building the app in Release mode and not debug. And the same goes for the setup project. ?
Good Luck

[Craig Gemmill]

Ok I lied. Heres the deal. In Beta1 this was done automatically. Now you have to pull a file called "dontnetfx.exe" off of your .NET install cd labeled 'windows components updates'. You then have to include it with your setup media and instruct the user to run 'dotnetfx.exe' before trying to install your program. This can be done with autorun.inf if you please. The reports say that ms plans to distribute the .net framework with all their new apps and service packs which, I suppose, is supposed to give us some hope that the .Net framework is on the the client machine... uhh no. This sucks but oh well.

Heres a refrence:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/html/dotnetframedepguid.asp

Good Luck

[John G Duffy]

Thanks Guy.
FFOund the package. 21+MB? seems like an awful lot to ask of a 4.3Gig hard drive don't it.

'
'
Please rate it if it answers the question
or is useful.
'
John G

[John G Duffy]

Took your suggestion, Installed the dotnetfx.exe and tried to execute the .msi file according to instructions and got real ugly message.
Dblclicked the Setup.exe and everything installed properly and the APP actually works.
Thanks.
Will let speeping dogs lie for now

'
'
Please rate it if it answers the question
or is useful.
'
John G

[Iouri]

If you installed .Net Framework on Win.ME(or Win98) you can do 2 things:
1.Just copy .exe file from your development machine. It will run
2. Create installation package (inside the VB.NET IDE). You don't need PDW for that and run the installation. .Net Framework will install Visual Installe 2.o to the target machine.


The main idea of running the installation package is to achieve the extart functionality like creating shortcut on the desktop, adding shortcut to the Program Files, adding entry to the Control Panel for application removal etc. If you don't need it you can just copy the exe file

Iouri Boutchkine
iouri@hotsheet.com