Package And Deployment

Developer Client

System System

Applications C:\My Software

To copy it
we need registry
This Exe Files
Exe Files
Contains DLL Files
DLL Files
all these Txt Files
Txt Files
files ------
------
BMP Files Copied into it BMP Files
called as XCopy
Deployment
 When it comes to Xcopy deployment the user has to perform
manual registry entry to avoid this set up creation has been
introduced.
 When you create a setup for the application then it is called as
packaging
 When you run the setup in the client system then it is called as
Deployment
 VB 6.0 will support Cabinet{CAB} based setup when the
installation process is terminated it will not perform
UnInstallation implicitly
 This problem has been overcome by introducing MSI setup ie
windows installer package setup.
 .net framework supports different types of set up projects
1} setup project
this is MSI setup for desktop application
2} Websetup project
this is MSI setup for Web Application.
3} Merge Module project
this is MSM setup for libraries
4} .CAB setup
 Merge Module project will be used for packaging libraries with a
particular version. This will produce MSM file. This setup can not
be taken Independently to the client system. This has to be
related with MSI setup.
The advantage of this is packaging a particular version of
library where the library can undergo changes with new version.
 CAB setup is used when we want the application to be placed
for downloading on the web.
 1  Go to solution explorer on right click on the solution and
select Add  and then select New Project
 Setup and deployment and select
 Setup Project
 2  Now we get FileSystemOnTargetMachine and underneath
you have
 Application Folder
 right Click
we get Add  Project Output
 Select the { file Name }
 Click OK
 3  Now again select FileSystemOnTargetMachine { this is for
if you have any assembly which you have to install in GAC }
 right click
 ADD Special Folder
 Select Global Assembly Cache folder
 and select the files which are
present in the Application folder drag and drop into GAC folder.
Note  when we place Shared Assembly into GAC folder at the
time of installation the assembly will be placed in the GAC of the
client system.
 4  In set Up some times we may require some TXT files,BMP files etc
for this do the following 
Select Application Folder
 Right click
 Add
 File
 Add the files with .RTF{rich text format},*.bmp
etc.
 5  In VB6.0 short cut cannot be carried with setup where as in dot net it
is supported to do,follow the steps 
Select Application Folder
 PrimaryOutputForClientAPP
 right click
 Select Create Short Cut and give name
 Now drag and drop this short cut in
the Users DESKTOP folder.
 6  The menu can be created under programs option of the start button.
For this Now again select FileSystemOnTargetMachine
 Application Folder
 Users Desktop
 Users Program Menu
 right click on it and select ADD Folder
 And give some name “My software”
 Now under user programs menu we
see “My software” right click  Add  project Output  your name  OK
 7  If we want to have any dialog box or any logo etc we have
to go
In the menu
 Select View Menu
 Select Editor
 Select User Interface {we get a dialog box }
 Install
 Start  right click
 ADD Dialog
 Select SPLASH AND READ ME.  select OK
 8  Now under Start  we get Splash  Go to Properties
Splash BitMap  Browse the file {*.bmp}
 9 Now under ReadMe  go to properties  ReadMeFile
browse and select { *.rtf } files.
 10 And then BUILD THE FILE WITH THE SETUP NAME .
 Now go to the debug or release folder and you find the setup
files.
 Save it on the desk top or in the clients place and then you get it
installed.{ you can see the short cuts in the desktop.
 Microsoft is providing redistributable package called as
“DOTNETfx.exe”.When we run this dotnetfx.exe in the client
system it will install the baseclass libraries and CLR required for
dot net application execution.
 When we want to execute dotnetfx.exe along with setup then
provide “INI file” for the setup.
This INI file contains the fxPath = dotnetFx
msipath = {clientAPPsetup/your
name …}
 When the application is having is having crystal reports the
setup should carry “crystal report engine” for this Microsoft is
providing four Merge Module files (I.e MSM Files } include this
files in to setup project.
 MSM files will come with dot net framework installation we can
see this under
c:\program files\common files\merge modules

Crystal..msm Crystal..msm
Solution Explorer

Normal One
Solution ‘Client App’

Client APP
Setup Project
Client App Setup..
Right click it

ADD Merge Module

Repeat this process

till you include all four
modules

Now Build  Build Client App Setup/…your file name