I have explored both the VS macro's and environment vars, and VS will
not resolve the paths for either in the vdproj file, which is pretty
pathetic since the .vcproj files are full of VS macro references.
I am aware of the direct link to the project output when the setup app
is part of the project solution. In my case the setup projects have
there own solution and references the files via the "file" link cause
the "primary output" link is not available when outside the product
solution. This is by design such that the setup work needs to be
indepenant from the project solution work.
Sounds like I'm screwed. I just knew using the VS installer would be
trouble some and a half baked solution....
---JHG
[quoted text, click to view] "Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message news:<em1suHgPEHA.3100@TK2MSFTNGP10.phx.gbl>...
> I don't believe so. I think you mean VS macros that refer to solution and
> project locations, not environment variables. The only option I know of
> that's close to that is to set the setup project's input to be the output of
> another project.Right-click on the project name and choose Add Project
> Output. If they are in the same solution I think that debug/release choice
> hgappens for you.
> --
> Phil Wilson [MVP Windows Installer]
> ----
> "Joe Goeke" <joe_goeke@hotmail.com> wrote in message
> news:77e8692f.0405191255.4d84c5f6@posting.google.com...
> > I have several Visual Studio setup projects that reference product
> > output folders which of course include the sub dirs "debug" and
> > "release".
> >
> > The VS installed doesn't provide any mechanism to reference files via
> > environment vars. Is there a way to specify an environment variable
> > in the setup .vdproj file such that VS will find the files?
> >
> > I really don't want to have to clone and maintain two setups just to
> > differentiate between a debug and release product files.
> >
> > Thanks in advance!
