VS10 beta 1 - the Microsoft.VsSDK.targets revisited
***Disclaimer: This information applies to Visual Studio 2010 Beta 1 only.***
The first that you notice when compiling a VS package project is that the compilation is really *fast*. Really much faster than compiling an VS 2008 VS package.
This is mainly because of two important changes in a VS package registration:
- There is no package registration with the regpkg utility
- There is no devenv /setup execution
The updated VS SDK msbuild targets now include the following list of actions in order to support the F5 experience:
- If a VSCT is present in the VS package project
- Create pkgdef file
- Create VSIX manifest file
- Create VSIX file which includes
- Project assembly
- Project references
- pkgdef file
- VSIX manifest
- All items with build action set to “Content”
- Deploy VSIX to user extensions
- It is deployed under %LocalAppData%\Microsoft\VisualStudio\10.0Exp\Extensions\%Company%\%Package_Name – Package_Guid%\%Package_Version%
- Enable the extension
- The key HKCU\Microsoft\VisualStudio\10.0Exp\ExtensionManager\EnabledExtensions\%Company%\%Package_Name – Package_Guid%\%Package_Version% is written
After the VS project is compiled you can hit F5 within VS and another instance of VS (pointing to the experimental hive) will start and our extension will be there, enabled and ready to run.
Pablo
