Rob Relyea: WPF Tools

Josh Twist: Xaml Editing with Intellisense with no VS Designer

Fri, 08 Feb 2008 17:42:43 GMT

I knew you could change the default from WPF Designer to XML Editor (and lose all the intellisense), but I didn't know this tip that Josh shows about Xaml editing in VS...

2007 brought great work in WPF/Xaml Tools & WPF

Sat, 12 Jan 2008 11:13:48 GMT

Lots of progress in 2007 from Microsoft and the community in the tooling front

VS 2008 shipped with a Wpf Designer & a Xaml textual editor.
The Expression team shipped their first version in May and continues to improve Blend with previews of Blend 2 December Preview and Blend v1 SP1
Zam 3D is now shipping v1.
Mobiform shipped Aurora XAML Designer v1.
Robby Ingebretsen shipped a completed KaXaml 1.0 (that at least one dev is raving about: Kaxaml: The XAML editor for me).
Lester Lobo updated XamlPadX (first one to get to v3!)
Charles Petzold has XamlCruncher v2 shipping.

Debugger Visualizers

Mole for Visual Studio is a WPF runtime inspection tool in the same ballpark as Snoop, but integrated into VS as a Debugger Visualizer.

I need to go update my list @ http://robrelyea.com/xaml/editors

while (!perfect)
{
    UseThem();
    GiveFeedBack();
    GetImprovedVersions();
}

Use your favorites. Give feedback to their creators. Iterate. :-)

[please let me know if I completely forgot any tools...and sorry in advance]

The Platform?

Meanwhile, the WPF team shipped our first version in November 2006 (.Net 3.0), our first update in November 2007 (.Net 3.5) and we're all busy working on our next release wave...more public news @ Mix.

2008

I'm looking forward to the improvements that 2008 will bring to WPF developers!

[Updated the list:

upgraded the Blend link to their December Preview.
added Aurora

]

ZAM 3D 1.0 Now Available

Thu, 13 Dec 2007 14:44:07 GMT

I was happy to hear that ZAM3D 1.0 is now available for purchase...looks like you may be able to save 25% if you buy before the new year.

An email that I received says:

ZAM 3D Key Benefits:

Provides an easy to use 3D authoring environment for designers and developers
Offers both basic and advanced 3D modeling and animation capabilities
Converts existing 2D artwork in the AI and EPS formats into 3D models
Imports pre-built 3DS and DXF models for quick conversion to XAML
Outputs 3D XAML markup that integrates seamlessly with Microsoft Expression Blend and Visual Studio 2005 and 2008
Leverages WPF, the presentation subsystem for Windows Vista (also available on XP), to enhance application interface design

“Electric Rain’s product brings powerful 3D modeling and animation capabilities to both the creative designer and application developer, and will offer exciting opportunities for creating superior content and rich user experiences for Windows Vista.”
Forest Key, group product manager of the .NET Developer Product Marketing Group at Microsoft Corp.

Those of you doing 3d work in WPF may find it useful in your work. Congrats to the Electric Rain guys!

Xaml Editor in VS2008

Wed, 21 Nov 2007 11:52:39 GMT

As a guy who spends a lot of time thinking of Xaml, I'm absolutely thrilled that we've shipped VS with a "Xaml Language" aware text editor. You'll remember that since PDC 2003, we've been providing an XSD and having users use the Xml editor in VS. The major downside there was that with new Types (custom controls and 3rd party controls) didn't work with intellisense, and actually broke intellisense inside their content as well.

Now, the Xaml Editor can deal with new Types - I believe it can even deal with types that are described in the same project that you are using them!

Walt writes 2 posts that are a must read if you ever edit Xaml in VS:

Great stuff!

Try it out, and please give feedback on the Xaml Editor at the WPF Designer ("Cider") forum.

VS Debugger Visualizer for WPF: Woodstock

Tue, 20 Nov 2007 10:31:41 GMT

If you've liked Pete Blois' Snoop to help debug/understand what is happening in a WPF application, Josh Smith has recreated a subset of its functionality and integrated it into VS as a Debugger Visualizer. Read all the details on his codeproject posting for "Woodstock for WPF" and Josh's Woodstock announcement to the WPF Forum. Great to see!

Internal Mailbag: How to work with sample data in Blend/Cider

Wed, 10 Oct 2007 09:23:00 GMT

Internal mail that may be helpful to the WPF community, read bottom to top...if you have good tips (or feedback) in this area, please let us know...

---------------------------------------------------------------------

From: Blend Program Manager

If you are using ObjectDataProvider, use the GetInDesignMode flag to figure out when you code in running inside Blend/Cider, and change the behavior from run-time to design-time data.

Look at System.ComponentModel.DesignerProperties.GetInDesignMode()

---------------------------------------------------------------------

From: Microsoft User of WPF
Subject: Best way to have test data show up in blend but not at runtime?

I’m sure this has been asked before, but what is the best way to allow a designer to work with real clr data in blend without having to run the application to see the results of his edits? I’ve been using an object source for blend:

<Window.Resources>

</Window.Resources>

But when I run the app, I want programmatically generate data to show up. Any way clean way to do this without writing a bunch of custom login in OnLoaded that changes datasources and datacontexts?

Generally how do people deal with this problem?

Wanted: .RC to Xaml converter

Wed, 05 Sep 2007 15:25:50 GMT

A customer is looking for a RC to Wpf/Xaml converter. It looks like http://dudelabs.com has a converter to go from RC to WinForms, but I'm not aware of a RC to Wpf/Xaml converter.

Anybody have any techniques to share in this area?

Himalia: high-abstraction level User Interface Builder

Fri, 31 Aug 2007 02:00:11 GMT

Via this link that mentioned Xaml, I found http://Himalia.net. Sounds interesting...

Jaime Rodriguez: 2 WPF Tools Screencasts

Tue, 21 Aug 2007 21:27:27 GMT

Jaime Rodriguez has 3 new posts with some nice demos of VS 2008 Beta2 & Blend.

What's new in Beta2 ... ( lotsa new features ) - post on C9 [wmv]

How to build a WPF app using Cider AND Blend ... ( sweet spots for each tool, brief demo of the workflow) ..post on C9 [wmv]

Cider extensibility and features for control hosting, design-time, etc.. (screencast available if you were a TechEd attendee)

I love to see every new feature that helps WPF developers! Tell us what else is most critical to do...lots of work to still do.

[links to the c9 screencasts originally via VincentHome]

Event handlers support in VS 2008 for WPF applications

Mon, 20 Aug 2007 21:30:44 GMT

In September 2006, I posted how to "Add Event Handlers in VS for WPF". Thankfully, VS 2008 Beta2 now has support for events throughout the WPF design experience. Andrej Tozon posts with pictures describing some of that new support.

Source Code Outliner Power Toy for VS

Sat, 11 Aug 2007 13:18:01 GMT

In a recent VSX Community Newsletter I found a pointer to a Source Code Outliner Power Toy for VS on Codeplex. Haven't tried it yet, but looks interesting...

Multitargetting in VS2008 & WPF

Tue, 24 Jul 2007 11:22:01 GMT

As I mentioned the other day, beta2 is coming soon...VS2008 is the first version of VS that will be able to target multiple versions of the .Net Framework (2.0, 3.0, or 3.5).

A bit of background info:

Luke Hoban, a PM on the C# team who headed up the MultiTargetting design for VS 2008, did a blog post talks about multitargetting in VS: http://blogs.msdn.com/lukeh/archive/2007/06/29/net-framework-multitargeting-in-visual-studio-2008-aka-orcas.aspx
Faisal Mohamood, a PM on the MSBuild team, did a post about msbuild’s angle on multitargetting: http://blogs.msdn.com/msbuild/archive/2006/11/15/multi-targeting-how-does-it-work.aspx

WPF Significance:

When you use VS 2008 Express Editions (C# Express, VB Express), I believe you will only be able to target .Net Framework 3.5 for WPF apps.
When you use VS 2008 Pro, etc..., you will be able to target WPF applications that require .Net Framework 3.0 or 3.5.

Thomas Lebrun: Context menu in VS to launch a project in Expression Blend

Mon, 23 Jul 2007 14:31:27 GMT

Thomas posted an addin for VS to launch a project with Expression Blend. Cool.

What other productivity enhancers have you thought of that you'd like to build; or would like somebody else to build?

I'd like to see better shell navigation between a bunch of projects, with the ability to launch in Blend/VB/MsBuild, etc...in fact I built this a while ago...I just need to go spend some more time on it...

Delphi/C++ Builder Roadmap - There is a mention of .Net 3.0...

Wed, 27 Jun 2007 12:40:42 GMT

in the Delphi and C++ Builder Roadmap, but it still isn't clear when/if WPF will specifically be supported, and how. I'll see if I can get clarification...

Bob's Delphi Stuff posted how to do a code only WPF application in Delphi in September 2006. I'm curious if/when Delphi will add the necessary support for markup compilation (codedom, msbuild targets, etc...).

9 steps to finding/downloading/using a sample from sdk...

Mon, 25 Jun 2007 22:04:11 GMT

Any feedback on these steps? Do most of you just download all the samples from the SDK? Have you seen the Windows Client SDK teams post about finding the right sample from the "all samples" install. Any feedback in this area?

Typed "Wpf TextBox Sample" in the IE7 search box.

Navigated to TextBox page in MSDN:

Clicked on link to TextBox samples:

Clicked on a link to "Counting Text Changes in a TextBox Sample":

Prompted for an Exe Download, clicked on Run:

Read/Accept License agreement:

Choose location to unzip the sample to:

Open the files in Explorer:

Open in VS/Blend/etc...

Making Blend + VS 2008 work nicely together - using Blend Configurator

Wed, 20 Jun 2007 15:03:04 GMT

I hadn't realized that the Blend team released the Blend Configurator. If you are using VS 2008 and Expression Blend, this will make you happy. [via Pete Brown]

VS 2005 Extensions for .Net 3.0 - will they ever be updated or final?

Fri, 15 Jun 2007 11:58:11 GMT

Thought that we should clearly communicate this externally, in case there is confusion...(internal mail thread, please read bottom-to-top):

From: Me
The plan is that the delivery we made in November 2006 was the last update of those extensions.
VS 2008 (formerly code named "Orcas") is where all of our time and energy is going for great WPF tooling support inside of VS.
Yes, you may share this info.

From: MS Employee
Could you please give me a piece of advice – what is expected timeframe of shipping Visual Studio Extensions for NET Framework 3.0 RTM and may I share it with our local User Group?

Did I mention that Expression Studio shipped in May?

Sun, 10 Jun 2007 13:44:30 GMT

In the craziness that was Mix07, I don't think I ever even said that Expression Studio (Blend, Design, Media, and Web) shipped in early May 2007.

microsoft.com/expression is where to start.

How to get it:

Download the 60-day trial.
Buy Expression Studio (or just individual components).
MSDN Universal subscribers will get a copy of Blend due to many requests.
I also believe that Expression Studio is distribute as part of the MS Partner distribution. (don't know the formal terms around this...)

Debugging WPF's Element Tree

Tue, 29 May 2007 14:10:14 GMT

David Sleeckx posted a "WPF Tree Debugger Visualizer".

Does running as a Debug Visualizer provide a significant benefit to you all?

Pete Blois' Snoop should also get a look for people who want to see the runtime state of WPF's Tree.

Would love to hear what VS "Orcas" and Blend should do to get more helpful in this area....

Expression Design Feedback - Import from Xaml, Save as XPS, what else?

Thu, 24 May 2007 10:25:21 GMT

I've recently seen feedback on Expression Design that has asked for Import from Xaml and Export to XPS.

What other improvements do you want to see covered in future versions?

One issue I can contribute:

when I create a rectangle and then export to Xaml, why do I get <Path /> elements instead of <Rectangle />. Most things can be converted in Paths, however, I'd prefer to only do that when it needs to.

Granville Barnett: Likes preview of an element in the WPF Designer ("Cider") in VS "Orcas"

Mon, 21 May 2007 18:28:31 GMT

Nice photos of a cool feature: http://gbarnett.org/2007/05/21/cider-wpf-tools-for-orcas.html

VS "Orcas" Beta1

Sat, 28 Apr 2007 04:01:39 GMT

Earlier this month, VS "Orcas" Beta1 was posted up on the Future Versions section of the VS site. I'm moving from the March CTP to Beta1 now...

Build great apps or we'll take Blend back :-)

Wed, 04 Apr 2007 11:53:06 GMT

Glad to see that Soma and team made a good decision here (Expression Blend/Web will be included for all MSDN Premium subscribers.) Soma forgot to mention though, that we did that with a condition...you have to build great software for your users or we'll take it back. :-)

P.S. Another hideous URL from MSDN: http://msdn2.microsoft.com/en-us/vstudio/aa718661.aspx

Orcas March CTP - random issue list

Mon, 26 Mar 2007 08:06:15 GMT

I'm building another demo and I'm finding a few issues with the march ctp...likely these are already known...but I will collect and forward them, just in case.

Discovery

Noticed a nice touch in the new Xaml Editor...it helps you create clr-namespace uris for assemblys in your reference assembly list. Start with xmlns:foo="...it will then suggest the list.

Issues

C# Application.xaml - needs to have x:Class="ProjectName.App" instead of just "App".
When TargetFramework=3.0, all new class files still have "using System.Linq;"
DocumentOutline - I want to be able to select a tag and all of its content...it has a select content, start or end tag. I want to harvest a DataTemplate from one page and put it into another. I guess that isn't too hard in the xaml editor too, but having the documentoutline makes me want to do this kind of operation, and tree movement as well...
Not positive, but: Seems that everytime I modify app.xaml then run, i have a runtime error. Build/Clean/F5 fixes it.
Application.xaml like this raised an error about blueGradient not being found:

<Application x:Class="App"
   xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
   xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
   StartupUri="StartPage.xaml">
   <Application.Resources>
        <LinearGradientBrush x:Key="blueGradient" EndPoint="0.438,0.033" StartPoint="0.446,0.008">
           <GradientStop Color="#FF3951B7" Offset="0"/>
           <GradientStop Color="#FF1E2E73" Offset="1"/>
       </LinearGradientBrush>
       <LinearGradientBrush x:Key="nearWhiteGradient" EndPoint="1,0.5" StartPoint="0,0.5">
           <GradientStop Color="#FFDDDDE8" Offset="0"/>
           <GradientStop Color="#FFFFFFFF" Offset="1"/>
       </LinearGradientBrush>
       <ControlTemplate x:Key="pane">
           <Border CornerRadius="20,20,20,20" Margin="10"
                Background="{StaticResource blueGradient}" Grid.Column="0">
               <Border Margin="2,28,2,2" Background="{StaticResource nearWhiteGradient}"
                    CornerRadius="20,20,20,20">
                   <ContentPresenter
                        Margin="{Binding ElementName=root,Path=Margin}"
                        Content="{Binding ElementName=root,Path=Content}" />
               </Border>
           </Border>
       </ControlTemplate>
   </Application.Resources>
</Application>

"Orcas" - Project/Add - Window/Page/User Control/Resource Dictionary

Sat, 24 Mar 2007 13:43:47 GMT

After years of VS 2005 + VS Extensions, I'm loving WPF focused improvements in "Orcas". The latest little thing I noticed was in the Project Menu or the Context Menu of a project in solution explorer.

VS knows Window, Page, User Control, RD:

WPF Tools Unite - on project level format...

Fri, 23 Mar 2007 18:37:29 GMT

VS "Orcas" has the opportunity to fix many of the issues that weren't possible or easy to fix with our VS Extensions for VS 2005.

One example of that is the project file format, and how "Page" items and Compile items are related.

Orcas is going to treat these like this:

<Generator>MSBuild:Compile</Generator>

<SubType>Designer</SubType>

</Page>

<DependentUpon>Window1.xaml</DependentUpon>

</Compile>

Expression Blend and 3rd party tools should eventually sync to this behavior.

Expression Blend RC is a must see...

Sat, 17 Mar 2007 20:54:34 GMT

Most impressive are the new samples - with source code, of course.

Karsten posted the samples so you can check them out without downloading Blend's RC right away.

How to Open the Samples in Blend

One tip, in Blend, to get back to the "start screen" to open a demo, choose "Help/Welcome Screen". When you open a sample with this technique, it copies the sample and you can then change the code without fear of being able to get back to the working state...

March CTP of VS "Orcas"/Expression Blend - running notes

Fri, 16 Mar 2007 11:37:10 GMT

These issues may be known already and might even be fixed already, but this is my running log of VS "Orcas" issues as I do WPF development. I plan to keep updating this post... (maybe you could post your own list of detailed feedback to the VS team?)

[Remember: I'm focused on any problems or wishes i find/think of...not focusing on good things in this post. I love Orcas and I want to see it get as good as possible.]

My Scenario

What am I building? A tool to convert XAML to Code. (link for picture, etc...)

VS "Orcas"

XamlIntellisense

It doesn't filter the list of valid attribute based on those already set.
Intellisense doesn't suggest custom types in the project that match the content model...for example UserControl1
Ctrl-K/D doesn't reformat my xaml
If I edit xaml while the app is debugging, then press f5, i expect it to run...it is already running, but i don't get any feedback (i'm using dual monitors and the app is running on the other monitor...maybe it is becoming active). this feels different than code...but i don't have time to analyze now...just want to write it down.

Property Grid in WPF Designer

More Properties: BitmapEffect/BitmapEffectInput/SnapToDevicePixels
- is the second set of properties in Cider....deempasize BitmapEffects...they aren't hardware accelerated!
Brushes show up in the property grid as "#FF00FF" instead of "Blue"...that is likely BrushConverter's (in WPF) fault...can it be worked around in the WPF Designer?
Would love to have Search like Blend...without that, really want alphabetical...would prefer search though.

VS Item Templates

Add New Item - Custom Control Template gave error: "this template attempted to load an untrusted component "WinFxCustomControlTemplateWizard"...

Debugging

[Just got this to work...not sure what the issue was before??? will keep my eyes open.] Can't seem to find how to create a Watch variable in debug mode (or before I run)

WPF Designer

When I edit simple styles.xaml in xaml editor (which is merged into app.xaml via a RD) window1.xaml doesn't show those effects.

Expression Blend

(right now, I haven't installed the RC yet...will do that soon and recheck all these issues)

I already have a style set targetting all TextBoxes, I try to edit a copy of a controltemplate of a textbox, it doesn't offer to add that Template to the existing style.
I wanted to edit the SimpleTextbox style (in a ResourceDictionary xaml file)...doesn't seem possible with the designer.

WPF

I'll put things that need to be made easier here:

Setting RichTextBox if I have a string should be this hard. Forum question. SDK post. Blog entry.

Using VS "Orcas" to Target .Net 3.0 or 3.5

Thu, 15 Mar 2007 12:28:50 GMT

I'm using VS "Orcas" March 2007 CTP for almost all of my development now. As I learn things about it, I'll post them...

It has worked fine for me side by side with VS2005 (i have sp1 + vista support installed), but there are dire warnings that it shouldn't be used on a production machine, so I would be careful...my machine is very pavable, even though I'd prefer not to do it. I think I read a blog that the 9-part install has a side-by-side issue involving sql, while the 7 part download and install didn't include sql, and thus it didn't seem to have problems. There is also a VirtualPC version of this available, I believe. Be careful...

Before you go on

Daniel Moth left great info in a comment see his post for the easy way...if it doesn't work on your machine, as on mine, see below for the manual way. Thanks Daniel.

Creating new Projects

Under File/New Project, the VS team has made available "WPF Application", "WPF Browser Application", and "WPF User Control Library". They have renamed winforms apps from "Windows Application" to "Windows Form Application".

You have a choice of Targetting .Net3.5 or .Net3.0. It defaults to 3.5. There is a menu that is a bit difficult to find, where you can change your framework version before you create the project. Choices include 2.0, 3.0, and 3.5.

I haven't looked at all the differences of the project files that are created, but the main thing is the reference assemblies differ for those different target versions.

.Net 2.0: references only .net 2.0 assemblies (wpf not possible here)

.Net 3.0: references only .net 3.0 assemblies (linq not possible here)

.Net 3.5: references all of .net 3.0 and adds System.Core.dll (where linq is)

It seems like the new project dialog remembers the last framework version you used and keeps that setting.

How do I convert a 3.5 project to 3.0

The first time I created a project, i created a 3.5 project. Since I want to publish targeting existing Vista users (and xp users with .net 3.0), I wanted to go back and change it.

I did the following:

1) opened each project file in my solution. Right click/Unload Project. Right click/Edit MyApp.*proj. Changed: <TargetFrameworkVersion>v3.5</TargetFrameworkVersion>
To: <TargetFrameworkVersion>v3.0</TargetFrameworkVersion>

Right click/Reload Project.

The System.Core.dll reference is now a warning...since it can't find it.

My guess is the Microsoft.Common.targets (part of the msbuild system that is controlled by your project file settings) switches the framework directory it searches for referenced assemblies from c:\windows\microsoft.net\v3.5.20212 to c:\windows\microsoft.net\v3.0, so System.Core.dll wasn't found.

Each .cs has a "using System.Linq;", which will raise errors now...remove that line.

New Category for Posts: "WPF Tools"

This post was my first under a new category: WPF Tools. I'll go back and change a few posts to this category name...]

Shouldn't VS "Orcas" default the texteditor font to Consolas

Wed, 14 Mar 2007 06:18:06 GMT

Perhaps I am mistaken...I've changed the setting and I can't tell the default anymore...but I would have thought that VS "Orcas" would have used Consolas by default...

Can somebody else confirm now that I have changed my setting?

VS2005: adding usings/imports

Fri, 09 Mar 2007 05:11:18 GMT

theADOguy points out a feature of VS2005 that I love...you know about it don't you?

Mobiform Aurora Designer ships

Wed, 07 Mar 2007 20:02:49 GMT

Ron DeSarranno, CEO of Mobiform, just announced that Aurora has shipped their WPF/XAML designer tool. Beyond standard XAML uses, Aurora distinguishes itself from all other designers right now by allowing you to host it inside of your app.

Congrats Ron and Mobiform!

Xaml Editor List

Tue, 06 Mar 2007 18:00:02 GMT

Here are a number of "Notepad" like versions of simple XAML editing tools. Each of these versions has a live visual preview of the WPF content specified via XAML.

Targeting WPF

XamlPad (installed via Windows SDK)
Charles Petzold's XamlCruncher (.application)
Lester's XamlPadX (.zip)
Robby's Kaxaml (.msi)
Zhou's XamlHack (.zip) [Thanks Zhou]
Valentin's XamlPad in Browser (.xbap) [Thanks Valentin]

Targeting WPF/E

Mike Harsh's WPF-E Pad (web page)
IdentityMine's CHATBlender (runs in msn messenger)

Am I missing any?

Update: I'd love to hear which you use, and why...

Of course, the more complete WPF/XAML editing experiences are:

Microsoft Expression Blend
Microsoft Visual Studio "Orcas", March 2007 CTP
Mobiform Aurora

"Fidalgo" to "Orcas"!

Thu, 01 Mar 2007 19:44:03 GMT

With the March CTP of VS "Orcas", there should be less and less reasons (I'm not aware of any) for most people to use the VS Extensions for WPF, WCF that last shipped in November as a CTP.

People are familiar with code names such as "Whidbey" and "Orcas". "Fidalgo" was the code name for the VS Extensions.

"Fidalgo" was the term that Alex Kipman and I came up with for the project.

What is Fidalgo?

It is the island just north of Whidbey Island...you can take a ferry from Anacortes, WA (on Fidalgo Island) towards Orcas Island (one of the San Juan Islands).

WPF Designer & XAML Intellisense

Try it out...please read more details and give WPF Designer ("Cider") feedback on this forum.

Adding Event Handlers in VS for WPF

Wed, 13 Sep 2006 13:20:22 GMT

"Cider" has yet to make it easy to add a click handler for a button in the style that most VB and WinForms developers are accustomed to.

Update: Beta 2 of VS 2008 added support for this (7/2007). See Andrej Tozon's post.

I list the best techniques you can use until the real support is in VS for both VB & C# Developers.
Please comment if you have other tips...

VB Technique

1) Add an element to the window1.xaml file, give it a Name

<Button Name="button1">Ok</Button>

2) Build (ctrl-shift-b)

This will compile the xaml file and create a window1.g.vb file in obj\debug\ that includes a partial class definition with the following line:
dim button1 as System.Windows.Controls.Button;
Now you'll be able to use that button from code-intellisense.

3) Open the code behind file (Window1.xaml.vb)

4) Use normal drop down to choose button1 and the click event.

The handler is created for you.

C# Technique

1) Add an element to the window1.xaml file, give it a Name

<Button Name="button1">Ok</Button>

2) Build (ctrl-shift-b)

This will compile the xaml file and create a window1.g.cs file in obj\debug\ that includes a partial class definition with the following line:
System.Windows.Controls.Button button1;
Now you'll be able to use that button from code-intellisense.

3) Go to the constructor for Window1 in Window1.xaml.cs and type:

button1.Click += [Tab][Tab]

(press the tab key instead of typing "[tab]")

4) Voilà

Your file will now contain:

public Window1()
{
    InitializeComponent();
    button1.Click += new RoutedEventHandler(button1_Click);
}
void button1_Click(object sender, RoutedEventArgs e)
{
    throw new Exception("The method or operation is not implemented.");
}