Myriad differences between debugging in InfoPath preview mode and in a browser

I can’t recommend strongly enough that if you’re doing InfoPath debugging, if something you’re doing with rules or code looks correct, but isn’t giving the desired behavior, try seeing how it behaves in the browser.  The InfoPath preview mode is nice to have, but I don’t understand why when something like rules firing doesn’t happen in preview mode, but does happen in the browser.  I’ve encountered other arcane differences, but I can’t remember them at the moment.  Publish the form to SharePoint and use the browser form.  It’ll save you time.

How to fix Visual Studio when CTRL F does not work

Alt + W + R

Window > Reset Window Layout

devenv /resetsettings

devenv /setup

How to solve problems with adding promoted columns on a form template with managed code

I found that the best way to solve problems where promoted site columns don’t appear is to deactivate the form template in Central Admin, remove it, and then upload the template again.  I had to delete the form library, but gladly there wasn’t any content, so it wasn’t an issue.  If you don’t delete the form library, when you add the template again, it will result in duplicate list columns.  To avoid that, I would use Gary Lapointe’s gl-deletelistfield stsadm extension, and delete each list column before you re-add the site content type.