InfoPath Development and Visual SourceSafe

[Paul]

Currently, I am working on a project in which I need to create InfoPath forms
with code behind. I am using Office 11 and Visual Studio 2003.

My concern is, once I check the InfoPath project in to Visual SourceSafe I
am unable to build the project without errors. It seems that when building a
InfoPath project in VS 2003 requires to update several files contained within
the InfoPath project (ie: manifest.xsf).

Is there a way to integrate with Visual SourceSafe that allows the build
process to execute without checking out the entire InfoPath project?

 

[Franck Dauché]

Hi Paul,

Indeed the manifest is modified (template version number needs to be updated
by default each time you are generating a new version of your template). If
you select "Do Nothing" on version upgrade, maybe it would help, but frankly,
you are better off checking out all files before compiling.

Regards,

Franck Dauché

 

[Paul]

Thanks for your quick response, Frank.

As of right now we are already checking out all the files before compiling
the project. This is not an ideal solution to this problem though as we are
working in a team environment with multiple developers and several InfoPath
projects in the solution.

In this situation we run into the issue that if I build the entire solution
I need to checkout all the files of every InfoPath project. In the scenario
that an alternate developer is working on one of the InfoPath projects and
has it checked out I am not able to build the solution.

Also, above and beyond this we have an automated continuous integration
build process. The automated build will fail if it can not check out all the
files of all the InfoPath projects.

Any help on a solution here would be greatly appreciated

 

[Franck Dauché]

Hi Paul,

It is an issue. My personal experience is:
Create one or several shared assemblies and create a series of IP projects
that people can check out and compile one at a time (with a reference to a
bin folder with the latest compiled shared assemblies). You can minimize the
amount of code in your FormCode and push all your logic in your shraed
assemblies. This way each dev can own one or several IP templates at any
time, but don't "lock" others from modifying the shared assemblies and add
code.

Does it make sense?

Franck