The team blog of the Expression Blend and Design
In Expression Blend 2, when you choose to edit a code file or insert an event handler for an event, by default, Visual Studio will be launched. If you have multiple versions of Visual Studio (VS) installed, though, you may find that a different version of VS than the one you intended to open will get launched. The most common case is where you have both VS 2005 and VS 2008 installed, but VS 2005 gets launched by Blend instead of VS 2008.
The fix for this involves editing your registry. From the Run prompt (WinKey + R), type regedit and press enter:
With your Registry Editor now running, navigate to HKEY_CLASSES_ROOT\VisualStudio.DTE.9.0\CLSID. Copy the Value Data from this key:
With that value copied, go to HKEY_CLASSES_ROOT\VisualStudio.DTE\CLSID, and overwrite its existing value with the data you just copied a few seconds.
This change should let Expression Blend know to launch Visual Studio 2008 instead of Visual Studio 2005.
Thanks, Jeetendra “Jeetu” Kukreja
In Expression Blend 2, when you choose to edit a code file or insert an event handler for an event, by
Are the 2 PM positions posted here in August still open?
Bookmarked, thanks for the info.
Expression is always looking for great talent. If you or someone you know is interested in a position similar to the ones listed earilier please send me your resume and contact information at joamason AT Microsoft.
196 Microsoft Team blogs searched, 97 blogs have new articles in the past 7 days. 218 new articles found...
After I install VS 2005, for work motives, Blend Uses It as the code behind editor instead of VS 2008, so I have been try it and WORKS!!!
Great!! Just what I need!!
Thanks for the info..
I followed the steps above exactly at no avail. I am running Expression Blend 2 and I'd like to edit event code in VS2008. Blend keeps trying to launch VS2005 and warns that I need to run it as administrator. I also changed the value of key:
I have .NET 3.5 installed. I know there was an issue with Blend support in VS2008 with versions above .NET 3.0. I was under the impression it was resolved. I'm not using silverlight, just WPF. I hope I have given enough information about the problem.
I'd appreciate some help with this.
You've been kicked (a good thing) - Trackback from DotNetKicks.com