Setup Projects

1 view
Skip to first unread message

kororos

unread,
Apr 13, 2008, 3:43:45 PM4/13/08
to DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting
Hello,

how can I prevent a setup project from cleaning the target folder
before creating the setup project? Can it not delete only the files
that it will generate?

The problem arises when in the target folder I have other
administration related folders/files like for version control.

Thank you

Andrew Badera

unread,
Apr 14, 2008, 12:36:54 PM4/14/08
to DotNetDe...@googlegroups.com
Do administrative materials really belong in a setup project target directory?
--
--Andy Badera
http://andrew.badera.us/ http://flipbitsnotburgers.blogspot.com/
and...@badera.us
(518) 641-1280
Google me: http://www.google.com/search?q=andrew+badera

kororos

unread,
Apr 14, 2008, 5:00:28 PM4/14/08
to DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting
Hi Andy,

thanks for your prompt reply. I have the same dilemma and I have asked
the same question myself. However, this is the situation:
1. I have the source code of a project I have been working on. This is
version controlled.
2. In the target directory (output of the build and not setup project)
I have the target also version controlled.
3. After a major or minor release of the software I want to keep under
version control the files being distributed in the setup project. This
is needed so that I know at any given time what source code has been
used to produce the setup files.

Then I thought... ok I could keep the files that the setup project
creates in a separate folder. However, as:
a) the version control (such as subversion) needs an "administrative"
directory in each directory being version controlled and
b) the setup project output is a multi directory structure (setup.msi,
setup.exe, directories with prerequisites)

...I cannot copy all the output of the setup project to a new
location.

The solution I am currently following is to compress the output of the
setup project (and therefore compact it in a single file) and then
copy it in a "distribution" directory which I have under version
control.

The whole process is rather messy and currently very manual. I would
like to be able to avoid to have to write lots of scripts.

Any help would be very appreciated and sorry for the long reply.

On Apr 14, 12:36 pm, "Andrew Badera" <and...@badera.us> wrote:
> Do administrative materials really belong in a setup project target
> directory?
>
> On Sun, Apr 13, 2008 at 3:43 PM, kororos <lkoro...@gmail.com> wrote:
>
> > Hello,
>
> > how can I prevent a setup project from cleaning the target folder
> > before creating the setup project? Can it not delete only the files
> > that it will generate?
>
> > The problem arises when in the target folder I have other
> > administration related folders/files like for version control.
>
> > Thank you
>
> --
> --Andy Baderahttp://andrew.badera.us/http://flipbitsnotburgers.blogspot.com/
Reply all
Reply to author
Forward
0 new messages