VS SDK v4 Product Backlog is ready for public review


Below I’ve pasted the VS SDK Product Backlog for version 4 of the VS SDK.  We’re planning to ship this version of the VS SDK in mid-December.  This will be the last revision of the VS SDK that supports VS 2005.  We’d love to get some feedback on these features and work items. 


The major areas of focus for V4 are to



  1. enable community collaboration,

  2. ease component vendor pain, 

  3. improve the user experience getting started with the VS SDK and

  4. get a start on some VS Orcas platform and SDK work. 

Those themes drove the decisions we’ve made so far, but we need feedback from VS SDK users to ensure we are driving toward a successful release for V4, so please don’t be shy about letting us know what you think of our plan.  There is, of course, much more we’d like to do, but have to combine a lot of competing priorities and limited resources in order to come up with the best update we can for this time-frame.  Your feedback helps us to understand how best to compromise on priorities and align resources.













































































































































































Category


Priority


Feature


Doc


10


Documentation Tech Reviews I


Infrastructure


20


Checkin suites coverage improvements


Infrastructure


20


Code Coverage Improvements I


Community


20


Community Content Plan (Forum Sweep)


Other Features


20


General Bug Fixing I


Community


25


Community Content Plan (Forum Ownership)


Component Vendor


25


Component Vendor Web Control


Component Vendor


25


Component Vendor Windows Forms Control


Power Toys


25


Ship Source Outliner power toy code for community collaboration


Component Vendor


26


Component Vendor Setup


Component Vendor


27


Component Vendor Toolbox


Community


30


Community Content Plan (Webcast, Screencast)


Iron Python


30


Event generation


Iron Python


30


IP Language Service – Code window dropdowns Webcast


Test


30


Orcas VS PIA redist testing


Other Features


30


Project Aggregator 2 fixes in Orcas


Power Toys


30


Ship power toys more broadly (not just in VS SDK)


Better OOBE


30


Update Sample Browser Spec


Community


40


Community Content Plan (Blogs)


Other Features


40


General Bug Fixing II


Better OOBE


40


Getting Started Docs


Orcas


40


Orcas SDK – Ship with Orcas CTP’s


Partner Content


40


Test Adapter Sample (VS IDE Host)


Test


40


Vista GDR (Beta)


Test


40


Whidbey SP1 (RTM)


Community


42


Community Content Plan (Team Chat 30 min)


Better OOBE


43


Update Setup


Component Vendor


45


Component Vendor Help Integration


Community


45


Connect VS SDK user to community shared source for PowerToys and other projects


Component Vendor


50


Component Vendor Component Versioning


Doc


55


Integrate Documentation Tools into SDK


Samples


60


Nested Project Sample (update from Archive folder)


Other Features


60


Project Systems/VSRegEx – Cloning Templates Fix


Iron Python


70


IP Project – BrowseWith context menu for HTML project items


Other Features


70


Project System Base Classes – Cancel build


Other Features


99


Dynamic Project Flavor Sample


Test


99


PPE testing of Orcas


Other Features


99


Setup/Deployment of Packages via Deployment Projects


Other Features


99


Update MenuAndCommands ref samples for ComboBox command type


Infrastructure


100


Code Coverage Improvements II


Doc


100


Documentation Tech Reviews II


 

Comments (6)

  1. Anonymous says:

    Allen has posted the current product backlog that we are hoping to accomplish for the Version 4 version…

  2. Anonymous says:
    Can be found here. This is the last version supporting vs.net2005 <br><br>...
    
  3. jl32980 says:

    Thanks for involving the user community in your planning process. Really appreciated.

    A few questions:

    1) Are the lower numbered items of higher priority?

    2) Given v4 is the last release for VS2005, what’s the impact of Orcas on API stability?

    Public information on Orcas is really sketchy – no roadmap, no platform level feature list, and available downloads are limited to GUI/DB areas. Please advise the VSSDK community on the roadmap for VisualStudio itself, e.g. enhancements to the architecture, project handling, debug engine, editor, etc. VisualStudio’s true strength lies in its deep C++ constituents and its ability to allow native language integration. Without that, people would have adopted competitor IDEs like IntelliJ. A little more information on Orcas would be highly beneficial to your users’ planning process.

    3) Would V4 support VS2005 SP1?

    4) If VS2005 releases SP2, would VSSDK be updated, or at least certified, to work with SP2?

    5) Is native Babel being end-of-lifed in favor of the C# version?

    6) Will VSL continue to be enhanced?

    7) Please elaborate a little more about the community related features. Are they being baked into the product?

    8) What do the acronyms stands for: OOBE, PIA, GDR

    Thanks.

  4. Anonymous says:

    We have just completed the planning for VS SDK 4.0 last week. My good dev lead has posted the plans on

  5. jameslau-MS says:

    Hi there, I am the PM on the VS SDK team, and I can help answer some of your questions.

    1) Yes, lower the number, higher the priority. Priority 10 is more important than Priority 20.

    2) v4 is purely targeted at VS 2005. It has nothing to do with Orcas API stability. However, it is our goal to make your packages as compatible as possible and we always avoid making breaking changes.

    3) Yes, VS SDK 4.0 will support SP1. In fact, we regularly do test passes with SP1.

    4) Yes, if there were ever a SP2, we will do test passes on that as well and make sure the VS SDK work well with it.

    5) Native Babel – I wouldn’t say that. The native babel serve a different need than MPPG and MPLex.

    6) VSL – We have no plans to continue to enhance VSL at this point. From the customer feedback we received, our customers prefer us to invest in the managed package framework.

    7) Community features – Ah… great question. We are still spec’ing these right now and we have nothing concrete to share at this point.

    8) OOBE is out-of-box experience. PIA is primary interop assemblies and GDR is Globally Distributed Release.

    Hope that helps.

    • James
  6. Anonymous says:

    Allen has posted the current product backlog that we are hoping to accomplish for the Version 4 version