I am not sure if this is the same problem but here is what I have noticed:
1. I am developing a domain-trust solution that is meant to run both in the browser and the rich client. I do not want full trust because I don't want to sign it.
2. The solution has code so I am developing in VS2005 with VSTO. I can preview the solution alright from VS during development.
3. Since the solution has code, it has to be admin-published before it can be deployed. I do that. During the admin-publish process in InfoPath, it saves the XSN locally.
This XSN is no longer usable - I get a security error that it is restricted. I am not sure why this is happening, perhaps an InfoPath bug, but my guess is that this XSN is not meant for consumption.
4. I deploy the XSN to Forms Server--enabled Sharepoint as an admin-deployed form
5. From Sharepoint I can open the form both in the browser and in the rich client
I hope this may provide some insight into the problem...
David Airapetyan / Software Services ArchitectQdabra® Software / Streamline data gathering to turn process into knowledge