InfoPath 2010 uses VSTO from 2005? Seriously?


  • I started working with InfoPath 2010 because I wanted to take advantage of the new design styles and some of the 2010 fixes. 

    After I opened Visual Studio 2010 and attempted to create an InfoPath 2010 Form project.  This is no longer supported?  There was a video on the Microsoft page with the Program Managers showing you how you will Design the form, add a VSTO source code project, and then to really crap things up, I have to save everything, then open Visual Studio 2010 to check the source in and out of TFS.


    Video from MS Team:

    I took a look at the VSTO application that I have with InfoPath 2010 and it's VSTO 2005?


    What's the deal guys?  This is really a huge failure/hassle.

    This should be part of VS 2010.

    When is this going to be resolved?  I shouldn't have to install Team Explorer 2005 to make a 2010 product work.


    Friday, July 22, 2011 11:31 PM

All replies

  • Hello Dennis

    im afraid this isnt getting resolved in 2010.  Not even sure if its resolved in 2013 although i doubt it will be seeing as there are no IP templates i can find in VS2012.  IP hasnt had much love from Microsoft in 2013, seems the only difference between IP 2010 and IP2013 is the Logo.


    Sergio Giusti

    Whenever you see a reply and if you think is helpful, click Vote As Helpful! And whenever you see a reply being an answer to the question of the thread, click Mark As Answer!

    Tuesday, December 18, 2012 8:57 AM
  • Dennis:
    This won't be fixed in 2010, and you don't need to run VSTO 2005, you can run VS.NET 2008 + VSTO.

    You can use TFS's Explorer integration to check-in / check-out directly from your file Explorer, if you don't like running Team Explorer to access TFS.

    But what you described regarding 2013 isn't correct, InfoPath 2013 has been updated to use VS.NET 2012, and no-longer uses VSTO 2008.

    Alternatively, one can use InfoPath 2013 + VSTO 2012 to edit InfoPath 2010 forms, just set your compatibility level to 2010.  Also note, if you go down this option, the project file generated by VSNET 2012 is slightly more advanced (and unreadable by VSTO 2008).

    jliu - -

    • Edited by John Liu Tuesday, December 18, 2012 12:15 PM
    Tuesday, December 18, 2012 12:13 PM
  • I would recommend to everybody to upgrade to InfoPath 2013 which is finally using more reasonable version of Visual Studio (2012).
    Friday, March 01, 2013 7:50 PM
  • And the part about Team Explorer. There is official way how to work with Team Explorer (Source Control), but in my point of view it's more joke than usable solution:

    1) Do your code job with built-in VSTO

    2) Save and Close VSTO & InfoPath 2010 and open .csproj project in Visual Studio 2010, open up Team Explorer and do all your check-outs/check-ins you need.

    I've seen really funny video of two MS guys trying to collaborate on one project this way. 

    Wednesday, March 20, 2013 7:26 AM
  • I think it's time to just call it what it is.  Total crap.  In InfoPath 2007, we had the ability to create forms with code in two methods.  InfoPath first, then code in the VSTO (which is a very limited editor may I add) or using Visual Studio 2005/8 to create an InfoPath 2007 Project.  This would give us the FULL IDE and allow us to have continuity of business and process across projects.  This is the intent of Visual Studio.

    The part that "rustles my jimmies" is the fact that this existed and worked very well.  It was all integrated and the debugging was superb.  Just to drop it's functionality without any real explanation and to get two "Microsoft Guys" on a dumb web video to explain how we are supposed to be inconvenienced is truly pathetic.

    The other best part is that in the InfoPath Project, we could have source control on ALL of the artifacts within the .xsn not jus the .xsn itself.  Fidelity is lost.  We've lost a lot of time and money not being able to do diff searches on individual .xsl View files or .xsd data connection files.  This is a "you dummy you" mistake by Microsoft.

    To really take a kick to the crotch, you have to manually convert the projects and bring all the artifacts over into the "new" methodology.

    I would love for Microsoft to release a patch putting this functionality back in.  It made working with InfoPath a dream.  Now it's just a night mare.

    I just looked at the available templates in my Visual Studio 2012 Pro (with SharePoint addons) and there is NO project for InfoPath 2013 Form.  InfoPath 2013 Add in is not the same thing.


    Thursday, March 21, 2013 12:51 AM
  • Hi Dennis,

    You installed first right? :)

    Anyway, you'll need this first before you can use VS2012 with InfoPath 2013:  

    Microsoft Visual Studio Tools for Applications 2012 RTM - Preview

    If you try to use code behind in 2013, it'll direct you to get these downloads.

    If you want InfoPath 2010 and 2013 to work together side-by-side, read my blog here on this:

    jliu - -

    • Edited by John Liu Thursday, March 21, 2013 2:45 AM
    Thursday, March 21, 2013 2:45 AM