In the previous post we demonstrated how to create an extensions package for Visual Studio and managed to view details of our package in the about dialog. In this walkthrough we'll actually get to the meat and bones of custom project types - referencing MPF for Projects and actually creating a custom project type.

Do you maintain a lot of programmatical artefacts that relate closely to what you or your team does? Maybe you have a XML files that store input for systems you’ve built, or some kind of EDI data that needs to be maintained in good order. If you’ve got lots of data of such kind and it could benefit from a user friendly editor or source control a custom project type might be the answer.

Someone at work recently created some nice templates to use in Microsoft Virtual Machine Manager to help us set up VMs, but instead of using the normal product keys they used multiple activation keys. These keys can be helpful when you only have a set number of machines to deploy - but they can only be used a set number of times and are then deactivated. In a testing environment where machines are frequently built and then thrown away this can mean your templates suddenly stop activating.