OK, so you've just decided that WPF is the strategic technology of choice for your next-generation application, and you've taken the opportunity to flatten and reinstall your developer workstation. What should you put on it to create the perfect WPF development environment? There are so many good tools, utilities and samples out there, that I thought I'd put together a little checklist that will hopefully help folk out. I'd love to hear your suggestions for anything that I've missed: I'll try to keep this updated over time.
Tools and Utilities
Building a Code Toolbox
I'm the kind of developer who likes lots of sample code available to me for copying concepts, ideas and techniques. Copy these to a \samples directory for quick access:
Also unpack %SdkTools%\..\Samples\WPFSamples.zip to a \samples\sdk directory so you can easily browse through all the samples without needing to go through the SDK documentation interface.
Now enable Windows Desktop Search (install WDS 3.0 here if you're running Windows XP) and configure it to index file contents of .xaml, .cs, .vb files as a bare minimum. Make sure it's set to index the entire \samples directory that you put the above samples into. Now you can quickly pull up every sample that shows the usage of (say) BitmapSource and ColorConvertedBitmap just by hitting Win+F and searching for those keywords.
Tips and Tricks
Thanks for all the feedback so far: I've incorporated some good suggestions, including the standalone link for the Consolas font and XamlPadX in place of the regular XamlPad.
In response to Parker's query, Expression Blend has a number of features that VS doesn't have in the current release (for example, editing styles and creating templates are manual operations in VS but supported by the Blend editor). Over time, you can certainly expect the two tools to come much closer to feature parity but remaining focused on their respective designer / developer audiences.
Another alternative to XamlPad is Kaxaml. You can get it here: http://notstatic.com/archives/64
A special Christmas Eve version to clean out my Feed Demon box as I will be on vacation next week and
I luv xamlpadx. it has the same feel of xamlpad but has more funtionality thn kaxaml. The interpreter is sweet.
Nice compile Tim
Ping back from samiqbits.blogspot.com
<i>As I've been blogging before I am working with WPF for a personal project. This has nothing to do with my 8-5 job, but is a nice thing to be doing in my spare time; anyway, the reason of this post is that by looking around I found this entry by Tim Sneath...</i>
Appunti di WPF: Building a Perfect WPF Developer Workstation
FYI XamlPadX v2 is out.. (http://blogs.msdn.com/llobo) .. its got some sweet new features :) Happy new year
Thanks to Tim I've probably got a few bits and pieces to install to get my machine up to dream spec for
I've just downloaded the Oracs (sorry Orcas - watched too much Blake 7 as a kid) Jan CTP but it does not seem to support the creation of WPF apps. Can you explain what you need to create WPF on Orcas.
Hi Andrew, the WPF designer isn't in the January CTP of Orcas, but you should see it in the next CTP. For now, Visual Studio 2005 is the best place to be. That's why you can't see it!
Tim Sneath : Building a Perfect WPF Developer Workstation このブログ記事では、完全なWPFデヴェロッパー向けワークステーションを構築するために必要なものがまとめら
Building a Perfect WPF Developer Workstation
Wer sich, wie ich, für WPF interessiert, und damit entwickeln will, braucht wie immer ein Set von Tools,