Handling of files created by a postbuild step in a setup

thomas woelfer · Post by **thomas woelfer** » Wed Jul 09, 2008 11:41 am

hi.

i'm using the current enhanced ide client and vs 2005. my solution contains several projects, one of which is a setup project. another project has a post-build step. that post-build step creates a file which must be redistributed by the setup that is created using the setup project.

i can simply add the file to the setup project (using add->file or add->assembly) and the file will than be packaged, shipped and installed. however, by adding it to the setup project, the file will also be added to vault - i.e. it will be under revision control after it was added to the setup project.

this, however, is harmful to my build process: because the (generated) file is under revision control, it is marked as read-only on the disk. that is, during the next build, the generation of that spefic file will fail.

i guess my question is: how do i add a file that is beeing generated during a post-build step in one project to a setup-project, without the file beeing placed under vaults revision control ?

WM_THX
-thomas woelfer

ian_sg · Post by **ian_sg** » Mon Jul 14, 2008 8:41 am

Thomas,

Is the file add being done by a script during a build? I'm a little unclear about what's happening.

After adding the file, removing it from the list of pending changes will prevent it from being checked in.

thomas woelfer · Post by **thomas woelfer** » Mon Jul 14, 2008 8:54 am

Ian,

thanks for your answer. the file is generated by a script during a post-build step in one of the projects involved. the file is included in a setup project (which is one of the other projects.).

basically, the question was: Hod do i add a file to a setup project in visual studio without the file becoming a subject of revision control in vault.

however, i just found a solution. (the file in question is an assembly and i just added a reference to that assembly to one of my projects; thus making it part of the "detected dependencies" of that project which are, by default, not under revision control.

WM_THX
-thomas woelfer

ian_sg · Post by **ian_sg** » Mon Jul 14, 2008 12:16 pm

That makes sense. Thanks for the follow up.