The Final Nail in InfoPath’s Coffin


If you have not read already, Microsoft has officially announced that InfoPath is to be no more after the current release. You can find the blog post on the Office blog here:

One key thing to point out in the posting is that they said it will be supported with SharePoint 2013, but not future versions of SharePoint. This should be writing on the wall to start thinking about how to migrate your InfoPath forms solution to something else. The question is what.  I have tried some other forms solutions out there for SharePoint, but they have a ways to go. I am a big fan of the SharePoint app model (Yes even now that I have left Microsoft) and I like the way Access 2013 builds apps for SharePoint.  Maybe something along those lines for apps is the way to go. For now, all forms related projects have now become IT driven products and have shot up the TCO of SharePoint due to the extensive amount of professional development work required to support custom form development.

We should hopefully know more at SPC14 and even more throughout the year.


My new home… well virtual home


I finally left Microsoft to start pursuing other adventures.  I really wanted to be back closer to Chicago to be closer to friends and family.  The good news is I have not left SharePoint and I will actually get to use it in real world scenarios. The bad news, I will feel the pain like every other customer out there. I am hoping the Cloud App Model in SharePoint 2013 will be my savior.

One thing that I am trying to look at is how to make SharePoint a complete CMS (Content Management System).  SharePoint 2013 does a lot for supporting browsers of all kinds on various devices and operating systems.  That’s great.  However the challenge is going to be, what if the content being managed is not rendered in SharePoint but instead somewhere else like an email. We don’t have the luxury of making everyone a user of SharePoint since we push public content to 100,000’s of users world wide.  We have to support it all and stay ahead of the SharePoint’s browser support curve.

I intend on posting our discoveries and lessons learned.  So stayed tune.

P.S. Yes I know there will be custom code.  That is a given