Create, Explore, and Survive with the Minecraft Licensed Merchandise Bundle

In August at select retailers, buy the Minecraft: Xbox One Edition Favorites Pack for $29.99 and get Minecraft licensed merchandise at no additional cost! In Minecraft, create and explore your very own world where the only limit is what you can imagine — just be sure to build a shelter before night falls to keep yourself safe from monsters. Take on new adventures by yourself or with up to three friends in split-screen, or play with up to eight players together online. Minecraft: Xbox One Edition Favorites Pack includes the base Minecraft: Xbox One Edition game and seven of the… Continue reading Create, Explore, and Survive with the Minecraft Licensed Merchandise Bundle

Watch the Gears Esports Offseason Finale on Mixer this Wednesday

On July 26th, Mixer and The Coalition launched the first ever Mixer-exclusive reality series, Gears Esports Offseason. The series consists of four episodes, three of which have already aired, with the final episode set to air this Wednesday, August 9th at 5pm PT/8pm EST/12am GMT on Mixer.com/ChannelOne. Each episode offers a unique perspective into the lives of pro Gears of War esports players during the offseason as they get set for Season 2 of the Gears Pro Circuit, and includes live player Skype Q&A following the broadcast. Episode 1 followed a group of players from various top teams as they… Continue reading Watch the Gears Esports Offseason Finale on Mixer this Wednesday

Why great inventions may need a village, but often a family

In the early morning hours of Aug. 5, 1888, Bertha Benz – yes, the Benz in Mercedes-Benz –  and her two teenage sons rolled the first patented horseless carriage onto the drive outside their home in Mannheim, Germany. Unbeknownst to her husband, Karl, Bertha was taking his three-wheeled contraption on a 60-mile journey that would…

The post Why great inventions may need a village, but often a family appeared first on The Official Microsoft Blog.

Continue reading Why great inventions may need a village, but often a family

Interview with Ginger Reinauer, UX designer at Expeditors  | GALs

Ginger is into anything and everything. By day, she works as a UX Designer in the emerald city of Seattle, but when night rolls around she lets her creativity loose on the world and frolics in the lands of 3D printing, embroidery, watercolor, children’… Continue reading Interview with Ginger Reinauer, UX designer at Expeditors  | GALs

Multiple Visual Studio Versions, One Extension

Carlos Quintero, Friend of the Blog, has written up a great MSDN Magazine article that’s perfect for our Visual Studio Extension Monday highlight…

Visual Studio – Creating Extensions for Multiple Visual Studio Versions

The release of a new version of Visual Studio is always a challenge for developers of extensions (packages, add-ins, templates and so forth). For example, Visual Studio 2010 introduced the new Visual Studio Installer for eXtensions (VSIX files); Visual Studio 2012 introduced the light/dark themes; and Visual Studio 2015 removed add-ins (with the Add-In Manager); not to mention that each Visual Studio version provides a new SDK, new extensibility assemblies and new APIs. With Visual Studio 2017, this challenge is even bigger, due to its new modular setup based on workloads and individual components, and to a new version of the manifest for the VSIX deployment mechanism. While some developers (most notably from Microsoft) release a different new extension for each Visual Studio version, most would prefer to release a single updated extension that can target the widest range of Visual Studio versions.

In this article, I’ll show you how to accomplish this. For this purpose, I’ll focus on the most common scenario: a package with a command, created in a managed language (C#, in this case) and deployed as a VSIX file.

The goals to be accomplished are the following:

  • To use a single Visual Studio project to create the package.
  • To use Visual Studio 2017 for development and debugging.
  • To generate a single package DLL as the result of the build.
  • To put that single DLL inside a single VSIX file.
  • To be able to install that VSIX file on Visual Studio 2017 and on many past versions (2015, 2013 and so on).

image

The VSIX File …

The Package DLL …

Developing the Extension …

Once you’re done with the development and debugging, you can build your extension in Release configuration and test it on Visual Studio versions installed in isolated instances on test machines. If everything goes well, you can then publish your extension on the Visual Studio Marketplace!     

[Click through to read the article]

Follow @CH9
Follow @coding4fun
Follow @gduncan411

Continue reading Multiple Visual Studio Versions, One Extension