I suggest you...

Visual Studio 2017 support for BizTalk 2016 projects

There are lots of improvements that would be great for BizTalk delivery teams to take advantage of.

83 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Charlie Mott shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    added to backlog  ·  AdminValerie Robb (Program Manager, Microsoft Corp) responded  · 

    Historically we add support for newer versions of Visual Studio in the next version of BizTalk and that is the current plan. As to the next version of BizTalk – we are doing our roadmap planning and it will likely be available in 2019 with a CTP version available at some point in 2018. These dates are tentative as of December 2017 and I will update when we have further information.

    14 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Rob Fox commented  ·   ·  Flag as inappropriate

        I just don't get it. Community developers are able to get their stuff updated to latest VS versions. how is Microsoft unable to do so? Just release it with a new Feature Pack... or make it open source. The community will take care of it.

      • Alastair commented  ·   ·  Flag as inappropriate

        There always seems quite a lag between Visual Studio releases and major BizTalk releases, meaning operating in old development environments. I think many BizTalk developers would appreciate updating of Visual Studio support as a feature update to rapidly coincide with a Visual Studio release - even if this still means targeting older .NET frameworks (I'm sure there is another request for more rapid targeting of new framework versions).

      • Allen Cook commented  ·   ·  Flag as inappropriate

        The extension system for Visual studio has been re-tool as of 2012 to allow for backwards compatibility, Why not use the .visx files to allow forward compatibility at least.

      • Fréderic Cordier commented  ·   ·  Flag as inappropriate

        Frankly, I would rather see a situation in which the latest version of Visual Studio supports the BizTalk tooling and SDK. In such a situation, when creating a new project, you would be able to target either BizTalk 2016 or 2013R2 from within a single version of the IDE. It is true to install multiple versions of the IDE side by side, but it still feels limiting and cumbersome to being restrained to a particular version of Visual Studio. We are already seeing that Visual Studio is essentially an empty shell that can host any number of development types (Windows, Web, Office, SQL,...). And while agreeing that BizTalk development require having the BizTalk application tier installed for being able to run these apps on the local machine, tight coupling as in today's approach feels a bit outdated.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Nice to have, but in no way a showstopper. VS has always run perfectly well side by side which most shops do anyway without realizing it :)

      • Andrew Lewis commented  ·   ·  Flag as inappropriate

        We keep seeing upgrades for VS like 15.4 and 15.5 coming out with features for other people. When will 15.BizTalk appear.

      • Christiaan commented  ·   ·  Flag as inappropriate

        It would be really nice to know when support for VS 2017 will be availible.

        We're planning to upgrade from BizTalk 2013 to BizTalk 2016. If this option will be availible soon, we will wait for it :).

      • Phile commented  ·   ·  Flag as inappropriate

        We are using VS 2017 for our application development now, we are really hope MS can update a new CU to support VS 2017 in BizTalk 2016. If not we must be deploy two version VS, it's too complex.

      Feedback and Knowledge Base