One recurrent feedback that I got from the community and users was that the price for the Visual Studio 2010 version was too high (used to be $19.99).
I always value user opinion, feelings and thoughts. Because I listen to what you say, I reduced the price to $8.99. Now you don’t have an excuse to buy it. 
Enjoy StickyNotes,
Pablo
I just released RapidMEF. If you use MEF heavily in your applications then this project is for you.
RapidMEF is a collection of tools to help developers author and debug applications that use MEF under Visual Studio 2010.
Features:
Runtime composition visualization
Some screenshots:
Filtered Intellisense
Augmented QuickInfo
Runtime composition visualization
Enjoy,
Pablo
Finally StickyNotes version for Visual Studio 2010 is now available. There is an upgrade path for existing Visual Studio 2008 users.
Features:
Enjoy,
Pablo
I am pleased to announce that StickyNotes version for Visual Studio 2010 is now available.
I like to invite you to try this version of the product, and experience the updated interface and new features.
Why should you try it:
You can download it from here
Please try it out and don’t forget to send feedback
Pablo
Today I received the confirmation email. I am a MVP again for Visual C#.
I want to thank my MVP lead Fernando Garcia Loera and the rest of people involved in the evaluation process for the recognition of my community efforts.
Thanks Microsoft!!!
Pablo
***Disclaimer: This information applies to Visual Studio 2010 Beta 1 only.***
This time I will talk about the new DSL extensibility feature in DSL VS10. This feature allows a model to be extended after it is deployed. This opens a huge number of possible scenarios including third party ones.
In this part I will cover the core changes and concepts in the new version of DSL to support the extensibility feature.
A DSL extension is indeed another DSL. This means that a DSL is extended by creating another DSL.
From now on I will refer to them as the extendee DSL and extension DSL respectively.
These are just a couple of extensibility points that can be provided (just to mention some of them):
But the real thing is that we can completely override the behavior of the extendee DSL. What really happen behind the scenes is that the extendee domain model plus all the extension domain models found are being loaded into the same store.
The new ExtensionElement domain class
In the runtime there is a new abstract class called “ExtensionElement” that inherits from the well known ModelElement. This class is used to represent an extension to a model element. It also called “MEX”.
The new “Extensions” domain relationship
The ModelElement was updated and now includes a new “Extensions” domain property. This is basically an embedding relationship between ModelElement and ExtensionElement.
MEX extension methods
Under the new Microsoft.VisualStudio.Modeling.Extensibility namespace, there are a couple of useful extension methods for the ModelElement class to do CRUD operation over the ModelElement extensions.
Next part : MEF, extension providers and how extension domain models are being injected
Pablo
***Disclaimer: This information applies to Visual Studio 2010 Beta 1 only.***
In the previous version of the VS SDK, when we create an Isolated Shell project, there is a command to specify Shell Dependencies:
When we compile the project, those dependencies plus any pkgdef file are being copied to the \PackagesToLoad subfolder.
Now is VS10, the Shell Dependencies command is gone and the way to add dependencies is via the References button. (which seems more natural to me)
Another change is that the PackagesToLoad subfolder was renamed to “Extensions” to be sync with the full IDE extension naming thing. :)
Pablo
