We are currently developing a configuration for CCNet for our projects
and all appeared to be going well until today.

The project in question is running fine with normal continuous builds
(fired after a check in to SVN) and a scheduled build which produces
MSIs using the devenv command. It has even flagged up a few failures
during the last couple of weeks of testing which has strengthened the
need for such a system/process.

Today one of the Devs checked in a new page (.aspx + code behind and
designer files) which was mapped to a menu option on the master page
(which was also checked in). The build completed and we produced an
MSI which installed without any problems. The problem arose when we
started the application and attempted to navigate to the new page -
enter yellow screen of death!

The source of the problem was simple to find - the new file was not
installed and checking back to the build server, not in the solution
for the project - although it was in the correct location in the file
system. The build passed because the file was only referenced in the
string value of the menu item.

We manually added the files to the project and saved the solution,
Forced the build to produce the MSI and sure enough this cured the
problem when installed on the test system.

Now to the question!

How do we add these new files to the project/solution (in a robust and
repeatable manner) prior to the build?

I'm sure we're not the first to encounter this - so please share your
knowledge :-)

Thanks in advance

Reply via email to