Jim @ imason

Internet Architect by day, environmentalist by night: Jim Schwartz @ imason.

Related Posts
  • NAnt, SharePoint and Production Deployments

    On my current SharePoint/InfoPath project, we’re using NAnt to deploy absolutely everything. NAnt creates SharePoint pages, imports web parts to pages, activates SharePoint features, deploys assemblies, creates SharePoint lists, creates/updates SQL databases (via DBDeploy ), packages and deploys InfoPath...
  • Advanced InfoPath Development with SharePoint

    Thanks to everyone who made it out to our Advanced InfoPath Development session yesterday at the Toronto SharePoint Camp . We had quite a good turnout; so I’m glad to see there are lots of other people out there using browser-based InfoPath forms using Forms Services on SharePoint. InfoPath makes...
  • Solving InfoPath "schema validation found non-data type" errors for xsi:nil fields

    If you try to programaticaly set/remove values of fields in InfoPath, you might have come across the following error message: "Schema validation found non-data type errors" A number of blogs and MSDN articles describe what to do in this case. They work for setting values, however I could not...
  • Changing the InfoPath 2007 file attachment control size limit in SharePoint 2007

    In my InfoPath page, I have placed a file attachment control on it for users to attach files with the InfoPath page they are filling out. The file attachment control seemed to have a built-in limit of 4MB as to the maximum file size the users can upload. I want to increase it to 25 MB. I found this post...
  • Automated Publishing of InfoPath Forms (Part 2 of 2)

    We’ve now surpassed 50 InfoPath forms on the InfoPath 2007 / SharePoint 2007 project I’m currently engaged on. If you’ve done InfoPath/SharePoint development before, you’ll know that it can be really painful to publish forms and then deploy them to SharePoint. In Part 1 of this...
  • How to Deploy InfoPath 2007 Forms with NAnt (Part 1 of 2)

    I've been using NAnt a lot lately for deploying components to development and integration machines. The common misconception that I've heard from reluctant SharePoint folks around here is that we should be packaging SharePoint solutions in WSP (SharePoint solution files) instead of deploying...