Visual Studio Extensibility Day 2019 was a hit

Mads Kristensen

Mads

On Friday, May 10th we hosted both internal and external Visual Studio extension authors in the Workshop room in building 18 on the Microsoft Campus in Redmond. It was a full day event with keynotes and sessions for 60 attendees – half of which attended //build earlier that same week, and half who came just for the Extensibility Day.

Attendees

They were a mix of old VSIP Partners, hobbyists, 1st-party MSFT teams and for-profit 3rd-party extenders. About half the attendees extended their stay for the //build conference to be able to attend the event. The rest came from all over the world and some flew to Redmond just to be able to attend Extensibility Day.

We’ve done similar events in the past exclusively for the VSIP Partners, but this was the first time we invited the larger extensibility community. For a lot of the attendees, this was their first time talking to- and socializing with other extension authors in person.

Agenda

To kick off the event, Corporate Vice President John Montgomery, and Director of Program Management Amanda Silver each gave a keynote. After that, sessions about various extensibility topics filled the rest of the day, including:

All sessions were highly technical and with lots of demos.


Amanda giving her keynote about the future of Visual Studio (photo by @kosmosebi)

After the session ended, we went to the Microsoft Company Store and Visitor Center followed by drinks and dinner at the Boardwalk restaurant in the heart of the Microsoft campus. People stayed until they closed.

Addressing pain points

During the day, the attendees helped identify their main pain points and produced a prioritized list of documentation/samples for us to provide as well as organizing our backlog of features to implement. Then they voted on the priority of each item and these are the results:

Top 5 missing pieces of documentation (in prioritized order):

  1. How to run and write integration tests
  2. How to debug and profile performance and memory issues
  3. DTE or IVs* – which one to use, how and when?
  4. How to access telemetry data collected by VS about our extensions
  5. How to target multiple versions of VS

Top 5 missing features (in prioritized order):

  1. Added integration test tooling
  2. Develop extensions in .NET Core
  3. Define VSCT from code instead of XML
  4. Marketplace extensions should have a private preview feature
  5. Ability to revert extensions to earlier versions

Remote-powered developer tools

A few weeks ago, we announce plans to enable a remote-powered developer experience for Visual Studio. It was met with great interest by the attendees who had a lot of questions as to how it relates to extension development. It’s still early and there are a lot of unknowns for us still to investigate. We’ll make sure to keep everyone in the loop as we know more. Stay tuned on this blog for that information.

Late notice

We sent out the invitation a bit late, so we were afraid that people wouldn’t be able to make it with such short notice. If you were among the people who couldn’t make it, I do apologize and ensure you that next year we send the invitations out much earlier.

Feedback about the event

The attendees filled out an evaluation form online after the event and the feedback was overwhelmingly positive. Everything from the list of sessions, the backlog prioritization, to the food served for lunch all received a top rating.

I really enjoyed visiting the campus and getting a chance to meet the team and other extension authors. I found that hearing about possible future direction for VS, participating in documentation/backlog prioritization and getting a broader sense of the ecosystem all really helped me answer questions about where to head next for CodeMaid. – Steve Cadwallader, author of CodeMaid

There were room for improvements too, and the top suggestions for next time are:

  1. More time to mingle and socialize with fellow extenders
  2. More hands on and Q&A time with the Visual Studio team
  3. Let the attendees vote on what sessions to see at time of registration

To summarize; this was a great event and I hope we can continue to do events like this every year. Thanks to all the attendees for coming and help making the day one to remember for all of us.

Mads Kristensen
Mads Kristensen

Senior Program Manager, Visual Studio Extensibility

Follow Mads   

8 comments

Comments are closed.

  • Ben Ruthig
    Ben Ruthig

    Hi Mads,

    Is there anywhere I can register to be notified about progress on the Top 5 missing features/documentation?  I’m particularly interested in…
    Documentation:
    – How to run and write integration tests
    – How to debug and profile performance and memory issues
    – How to target multiple versions of VS
    Features:
    – Added integration test tooling
    – Develop extensions in .NET Core
    – Ability to revert extensions to earlier versions

    Thanks,
    Ben

  • Avatar
    Michael Taylor

    One thing I’d like to see added to VS extension support is the ability to use the assemblies of other VS extensions. At this point the only way I can figure out how to get this to work is to ship the required assemblies as part of my extension. As an example I have a CodeRush extension for VS. CodeRush is a dependency so my extension cannot be installed without it. However I still have to ship the core assemblies from CodeRush that I depend on because if I don’t then VS will fail to load the extension. This causes versioning issues if a newer version of CR is installed since VS may be running the newer CR extension but my code is using the older version.
    It would be nice if there was some way (that was documented as actually working) to allow my extension to find and/or use the assemblies of dependent extensions without the need for shipping the assemblies. 

    • Mads Kristensen
      Mads Kristensen

      This scenario is already supported by the extensibility model of Visual Studio. However, it is up to the extension you wish to extend to implement. They usually will provide services you can request and code against and then provide binding redirects to avoid the version mismatch problem you described. 

      I would reach out to CodeRush to figure out if you need to make any changes or if they do.