In the following scenario, working with VS2005, TFS, InfoPath and Biztalk 2006 in one solution, the following issues occur:
- All files (.xsf, .xsd, etc) needs to be checked-out if you only want to edit the Layout of the infopath form
- It is not clear how to share the XSD between the InfoPath project and BizTalk (I did not find a way to 'link' the xsd like in regular VS projects)
- I find it more convenient to edit the schema in vs 2005 xsd/biztalk editor. however as soon as InfoPath opens the files are 'in use by another process'
- If you preview the form, the solution will not compile because the xsd is locked by another process. I have to switch back to VS2005, click oK to continue, then my infopath will preview.
In my opinion Biztalk and InfoPath should 'share' a schema and it shoud be possible to change the schema without having the schema in the infopath project.
I foresee creating multiple forms for one schema, there fore sharing the xsd-s. It looks like the 'sharing' should be done by copying (which is a rough way of sharing)
Has anyone tried xsd:import or xsd:include AS far as I understand InfoPath will still cache the XSD. What happens with the Cache if the referenced XSD is changed
Are there known or unknown solutions for this or can this group elaborate on how to practically navigate around the issues
Tnx,
Rene

Infopath project under source control/tfs
rikimaruXP
The workaround for the XSD editing issue is to have a copy of your schema elsewhere, then use Tools | Convert Main Data Source to import the schema after each update.
Thanks again for your feedback, it really helps us plan future releases to solve issues like these.
- Ned
[Microsoft]
ScofferX
Does Microsoft now support Infopath project under source control/tfs
regards,
Pawel B.
fredkarm
Hi Rene,
I asked the InfoPath team about your scenario and unfortunately, there is no work-around :-( However, the appropriate PM has been made aware of your issue.
Regards,
Darryn Lavery [MSFT]