Page view counter

Using Blend with Visual Studio

For the past six months or so I've been experimenting with and then "preaching" the idea of developing with two tools: Expression Blend for the UI and Visual Studio for the code.  This has paid big dividends for me in productivity and it fits in well with the Parts and States Model and with keeping a clear separation of visuals form logic.

PartsAndStates

I'm about to give a pair of presentation at DevConnections (hence my total lack of blogging!) and I thought it would be fun to see if I just perceive  an increase in productivity or I can actually measure that increase.  Thus, I decided to put together a simple form, using a number of controls placed in a grid, including a control from the new Silverlight Toolkit (specifically the AutoCompleteBox) and measure the time it took to create the form from scratch in Visual Studio and in Blend.

Here is what the final product looks like:

FormForBlendCompare

 

I created an entirely non-scientific test in which I filmed and timed myself creating this form first in Blend and then again in Xaml using Visual Studio.

My not very accurate timing is that it took about 40 minutes in Blend and 30 in Xaml, but I think if you eliminate the overhead of filming, it is more like 30 in Xaml and 15 in Blend. Note also that I have about 15 years experience with Visual Studio and about 6 months with Blend

In any case, this may well be a case of "Draw Curve, Plot Points," but it was interesting and fun to do and seemed to validate my impression that Blend is not only easier, it is faster. I'm off to DevConnections and will try to post from there, but will resume what I hope will be much more frequent (and entirely technical!) blogging once I get back, along with the long promised series of deeply technical videos and tutorials.

2009 will be a very interesting year.

Thanks. -j

Published Sunday, November 09, 2008 12:29 PM by jesseliberty

Comments

# re: Using Blend with Visual Studio

I really am surprised you guys have found yourself in the position of having 2 tools to do fundamentally the same job. At some point, you guys will "integrate" the functionality of Blend into Visual Studio, and then you'll wonder why they were ever separate. At it stands, the lack of designer support in Visual Studio really blows. The current approach of toggling between Blend and Visual Studio is rather absurd. Add to that Blend's total lack of source control integration, and you wonder what rookie was running the show. I love Silverlight, Visual Studio, and Microsoft in general. But this hodge podge of tools is just kinda dumb.

Sunday, November 09, 2008 6:49 PM by jackbond

# Silverlight Cream for November 09, 2008 -- #423

In this issue: Joseph Ghassan, Boyan Nikolov, James Bacom, David Justice, Jesse Liberty, Shawn Wildermuth

Sunday, November 09, 2008 8:29 PM by Community Blogs

# re: Using Blend with Visual Studio

Jackbond

I agree with you, it should be integrated, but it also makes sense as a separate product targetting designer. Both tools are great and MS will argue that those are targetting different people, which in a sense is kinda true, but what we have now is probably two incomplete tools.

Blend:

-Doesn't have good support to code (e.g. support nested projects, code editor, intellisense, at least create event handlers). Many web designers are used to do a bit of coding (e.g. Javascript, Action Script, CSS, etc). Even for them Blend should provide even more help, as they're not expert devs (e.g. code snippets, autogenerate code to start animations, etc)

-Lack Source Control support

-XAML Intellisense

-Proper tools to deploy your WebSite.

VS:

-No design support. Even developers need to be able to design a UI without switching. Probably complex animation, paths, etc could be left out, but at least allow the basic WinForm functionality. This might slow down the adoption of WPF and SL.

-Terrible WYSIWYG, sometimes it doesn't even show and when it does it takes forevent. Best thing to do is to open by default in XAML view.  

Together:

-Ability to use the same SC integration

-Don't ask me to refresh when I go from VS to Blend.

-Has the option to use the same shortcuts (e.g. Ctrl+Alt+L to see the Solution Explorer, F4 for the property window, etc). Similar to the way we can select the profile in VS to use VB.NET, C#, Tester, etc, we should be able to use a similar key binding profile for Blend.

-Same ToolBox experience.

The best thing to do would be to share the core functionality (Extension Model, Source Control, Plugins, Editors), similar to the way Expression Web and VS08 do. They have the same CSS windows.

For some web designers Expression Web might be enough, but a developer doesn't need to go to that product just for a couple of extra windows.

A probably more realistic approach would be to at least improve the workflow between the two tools.

Monday, November 10, 2008 5:05 AM by mamadero2

# re: Using Blend with Visual Studio

Isn't the reason that VS and Blend are separate a function of the different structure of each (Managed Code and WPF v Unmanaged Code and COM)?

If Microsoft is finally realising that Blend is an essential developer tool for Silverlight and WPF, why not grant a free licence to Blend to anyone running a legitimate licence for VS2008? Otherwise, you're discouraging use of the latest technologies.

Monday, November 10, 2008 5:10 AM by davidinnz

# Dew Drop - November 10, 2008 | Alvin Ashcraft's Morning Dew

Pingback from  Dew Drop - November 10, 2008 | Alvin Ashcraft's Morning Dew

# Dew Drop - November 10, 2008 | Alvin Ashcraft's Morning Dew

Pingback from  Dew Drop - November 10, 2008 | Alvin Ashcraft's Morning Dew

# Blend & Visual Studio

Pingback from  Blend & Visual Studio

Monday, November 10, 2008 9:57 AM by Blend & Visual Studio

# re: Using Blend with Visual Studio

Why not to separate it. This is what we want in the production. Separate Coding and Design.

I like it. like it is now.

Peter Loebel

Sunday, November 23, 2008 4:50 AM by SilverlightTravel