dotnet setup: I would like to build a basic setup for a VB.NET app but include one file
that will be different per user without rebuilding the setup every time,
just place the new file on the CD and have setup install it in the same
location as the application.

Any ideas?

Thanks,

Shane

How many files are we talking about here? I'm thinking that the easiest way
might be to have every file included in the installation and have conditions
that determine which one is installed.
--
Phil Wilson
[MVP Windows Installer]
[quoted text, click to view]

So how do you know which file the user will get? Do they choose somehow?
--
Phil Wilson
[MVP Windows Installer]
[quoted text, click to view]

I would just like to build my final setup and then throw one customized file
in the same location as the setup and have it copied into the app directory.

Or at least be able to easily change this file per client and add it without
rebuilding the setup for each person.

thanks,
[quoted text, click to view]

Phil,

I want to build a basic setup for the app. Have it in a directory. When I
get an order, I want to place one customized file relating to that customer
in the directory, burn the CD and mail it to them.

But I don't want to rebuild setup each time just for one file.

How can I do that?

Thanks,

Shane


[quoted text, click to view]

Shane, if the file will always be the same place on the CD, you could just add a custom step that copies the file from the CD to the Install directory
Unfortunetly Custom Actions require an executable or script to run. So I suggest making a quick script or EXE as part of your install that copies from the first
parameter to the second parameter.
Then include a custom action in your setup project that launches that file witht the arguments: "[SourceDir]MyFileName" "[TARGETDIR]"
You can add directories or wildcards as needed. This should solve your problem for you allowing you to copy files without rebuilding, it is however a little
bit of work.
------
Todd Derksen - VBQA Deployment Testing
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

| Phil,
|
| I want to build a basic setup for the app. Have it in a directory. When I
| get an order, I want to place one customized file relating to that customer
| in the directory, burn the CD and mail it to them.
|
| But I don't want to rebuild setup each time just for one file.
|
| How can I do that?
|
| Thanks,
|
| Shane
|
|
[quoted text, click to view]
| > So how do you know which file the user will get? Do they choose somehow?
| > --
| > Phil Wilson
| > [MVP Windows Installer]
[quoted text, click to view]
| > > I would just like to build my final setup and then throw one customized
| > file
| > > in the same location as the setup and have it copied into the app
| > directory.
| > >
| > > Or at least be able to easily change this file per client and add it
| > without
| > > rebuilding the setup for each person.
| > >
| > > thanks,
[quoted text, click to view]
| > > > How many files are we talking about here? I'm thinking that the
| easiest
| > > way
| > > > might be to have every file included in the installation and have
| > > conditions
| > > > that determine which one is installed.
| > > > --
| > > > Phil Wilson
| > > > [MVP Windows Installer]
| > > > "SStory" <TheStorys@TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in
| message
| > > > news:OcsDZ5wyDHA.2500@TK2MSFTNGP09.phx.gbl...
| > > > > I would like to build a basic setup for a VB.NET app but include one
| > > file
| > > > > that will be different per user without rebuilding the setup every
| > time,
| > > > > just place the new file on the CD and have setup install it in the
| > same
| > > > > location as the application.
| > > > >
| > > > > Any ideas?
| > > > >
| > > > > Thanks,
| > > > >
| > > > > Shane
| > > > >
| > > > >
| > > >
| > > >
| > >
| > >
| >
| >
|
|
|

Todd, thanks for the info. I will try this as soon as I can. Still putting
out fires with the app right now(debugging).

I was suspecting this.

Now, I should be able to write it in vb.net correct, because the install
will have to have the framework installed before it can install anything
else or will even call this custom action.... correct?

Thanks again,

Shane
[quoted text, click to view]
suggest making a quick script or EXE as part of your install that copies
from the first
[quoted text, click to view]
problem for you allowing you to copy files without rebuilding, it is however
a little
[quoted text, click to view]