There's a couple of areas that I know how to deal with when it comes around, but I don't really understand what's really going on with them so I'm hoping that someone can help me with these or point me to a place that discusses in detail. My environment details are: IP 2007 and MOSS/SP 2007.
Assembly name - This comes in with managed code and I know where in VS to change it when it barks that the Assembly name already exists when uploading to SharePoint. What causes that error though? What does SP do with these forms when uploading that it crosses paths with the assembly names?
Schema name/Form ID (looks like: urn:schemas-microsoft-com:office:infopath:myFormName:-myXSD-2010-02-10T17-12-10) - what does this do? I understand that when I want to use a 2nd form (say a new version of the original) in a library that the form ID has to be unique or an error may come up for users who have used both form templates. I see it show up here and there and have gotten the error for trying to run both form templates on the same computer because it's the same ID. I've also found that changing the ID in design mode doesn't do anything with the manifest and the other associated files, so even if I change it in design mode, I still see the old ID in random places like on uploading and error boxes.
Upgrade form - When uploading to SP there's an option to upgrade the form. What does this mean to upgrade the form? I've heard of people uploading a new version of the form and not checking that box and the old forms use the original template and the new forms use the new template, but it's the same form name and such.
Those are the top 3 areas that I could use some help understanding. Anything you can offer is greatly appreciated.
Karen.