How do administrator published forms work?

KarenSL — Fri, 20 Nov 2009 23:11:13 GMT

I have a form template that I've been working on for months and it's in production so the changes I make to it now are mostly just cosmetic and back-end code tweaks, there's been no changes to the schema, datasources or anything major. It's been said that I might've found an IP bug in upgrading forms with digital signatures, so before I corrupt anymore forms already in progress by upgrading, I thought I'd start versioning so forms already done use the template that it was created with, and new ones use the new template. My templates have code-behind so they're published in Central Admin, but I don't really have an understanding of what this means. I've seen errors such as the need to rename the assembly to messages saying it's been activated on the sites, and I know what to do to move forward (usually), but I don't know what's happening so when something goes wrong or I need to do something different like version the forms, I don't know how to best go about doing that.

So, my first question, is there a good tutorial on what exactly is happening with administrator published form templates?

My next question is to achieve the goal of template versioning, if I upload a new form, activate the feature for the site, point the "start a new form" button to the new template, will that achieve the goal of forms already created using their original template and new ones using the newly uploaded templates? Any gotcha's with that...other than the fact that over time I'll have a bunch of form templates and features started?

Thanks for any help you can provide. I know I need training, but I can't get that as quick as I need to continue moving forward with my project.

Karen.

Newbie Questions

How do administrator published forms work?