Jamie Kurtz

Moved my blog

Jamie Kurtz — Fri, 31 Jul 2009 13:07:49 GMT

I’ve moved my blog to here: http://www.jamiekurtz.com.

Using a prioritized backlog in the check-out lane

Jamie Kurtz — Tue, 19 May 2009 19:40:07 GMT

A few weeks ago I was in line at the grocery store behind a lady who was buying a fair amount of groceries. Pretty typical trip to the store, except that as I watched, she was placing her items (from the cart) onto the little conveyor thing quite atypically. Rather than just lining everything up one after the other, she was placing the items here and there on the conveyor. It seemed rather random to me. Until at one point, as she was closely watching the total price go up and up, she said “ok, that’s enough.” The cashier looked at her kind of funny, but the lady simply responded “that’s all I can afford”. So the cashier stopped – didn’t scan anymore groceries.

Apparently, she’d prioritized her load of groceries – either in the cart and/or as they were being placed on the conveyor. She knew what she could commit to, and she’d didn’t over commit.

Of course, it’s a little rude to then expect the grocery clerk to go and return all the lower-priority items that didn’t make this grocery “sprint”. But it was fun to watch!

Small Confession

Jamie Kurtz — Wed, 25 Feb 2009 02:43:11 GMT

I have a small confession to make...

A little TFS web service I built over the past few days was the first “real” production-ready application I’ve ever written from scratch where I’ve been good about maintaining unit tests. I even pushed myself to practice real-live TDD, and then even use Moq.

I have to tell you, that I am now a firm believer in the benefits of leaning very heavily on your unit tests. Of course I've always believed others' stories, and have even worked on projects/products where I had to maintain a fair set of tests. But not having ever really tried it myself – on a new project where I could create real isolated unit tests, I think my belief was kind of shallow. Sort of like… believing that the life vest will save your life before every really needing it. And then one day you find yourself involved in a boating accident and you awake after being unconscious in the water for two hours. Then you REALLY believe it.

I think this small experience will help me in conveying to others the incredible importance of building that unit test base. Because after only a few tests were written (and hence, only a bit of code written), I found myself getting nervous (as usual) making changes. But then I could flip to the Visual Studio Test View, run all the tests, and feel some assurance that I wasn't totally hosing things. Then as bugs would crop up during user acceptance testing, the very first thing I would do is write a new unit test that I knew would fail – based on the conditions I saw in the UAT. Then I would proceed to change the code until the unit test passed. What a great feeling!! And further, I know that anyone else making changes to my code will have to pass all the same unit tests – another very assuring feeling.

It really is amazing how much we screw up in code!?!?! Even the stupidest littlest things. There were times when I would think "This is lame, I don't need a test. But I'll write one anyway - and I'll write it before I even write the code." And then it would literally take me three or four tries to get the test to pass!! Crazy. Makes me very scared about all the untested code churn going on in the world!!

Oh, and using Moq was a real treat - it only took me a few unit tests to get the hang of it. Really helps reduce the time feedback cycles during development - as well as help in isolating your tests to smaller and smaller units (i.e. "unit tests").

Get going with Windows PowerShell

Jamie Kurtz — Sat, 03 Jan 2009 20:37:50 GMT

Today some quick tricks finally came together for me with Windows PowerShell. So I can finally write scripts and quickly execute them from the PowerShell shell.

If you haven't yet installed PowerShell, you can find it here: http://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx.

My simple goal was to be able to a) write a short script that can take parameters, and b) be able to easily run it from the shell. Here's what I did:

Close any open PowerShell windows
Add your script path to the Windows PATH environment variable. I'm using "C:\Users\jkurtz\Documents\WindowsPowerShell", but it can really be anywhere.
Make sure you have configured PS to run scripts. This page gives the details, but basically do the following:
1. Open up a new PowerShell window
2. Execute this: Set-ExecutionPolicy RemoteSigned
Create a simple script, named with a "ps1" extension, in the folder specified in step (2) above. I've included a sample script below
Now simply enter the name of the script at the PowerShell command-line (including any required arguments) and hit Enter

If you want to try it out, but don't have a script in mind, you can use this one. It's not the most useful script in the world, but it works for this example. Just use Notepad to create a file in your script path called "members.ps1", and paste the following contents into it.

param (
	[string] $domainname = $(throw 'please specify a domain name (can use . for local machine)'),
	[string] $groupname = $(throw 'please specify a group name')
)

$group =[ADSI]("WinNT://" + $domainname + "/" + $groupname)
$members = @($group.psbase.Invoke("Members")) 
$members | foreach {$_.GetType().InvokeMember("Name", 'GetProperty', $null, $_, $null)}

Then, if you've followed the 5 steps above, you can simply enter the following at the PowerShell command-line:

members -domainname DOMAIN -groupname "domain admins"

Or, leave out the -domainname and -groupname switches:

members DOMAIN "domain admins"

For a reference and guides to using PowerShell, here's some great resources:

Note that version 2.0 of PowerShell is coming soon.

2008 Team Explorer, SP1, and July 2008 Power Tools

Jamie Kurtz — Tue, 12 Aug 2008 18:53:13 GMT

Take my word for it, install all three of these (in this order):

The 2008 version of the Team Explorer
- Here: http://www.microsoft.com/downloads/details.aspx?familyid=0ED12659-3D41-4420-BBB0-A46E51BFCA86&displaylang=en
VS 2008 SP1
- Here: http://www.microsoft.com/downloads/details.aspx?FamilyID=fbee1648-7106-44a7-9649-6d9f6d58056e&DisplayLang=en
The July 2008 TFS Power Tools
- Here: http://www.microsoft.com/downloads/details.aspx?familyid=00803636-1d16-4df1-8a3d-ef1ad4f4bbab&displaylang=en

You don't need to uninstall the 2005 versions of Visual Studio or the Team Explorer or the Power Tools. The 2005 and 2008 versions can exist side-by-side. However, if you are a user of ONLY TFS - i.e. not a developer and don't need the Visual Studio 2005 C# / VB.NET stuff, you might as well uninstall the 2005 Team Explorer. But again, that is not required.

A few things to look for

Once you have the above three items installed, look for these great enhancements...

TFS Alerts

The Team Explorer now contains a great editor to create and maintain alerts for TFS events. So you can set alerts for check-ins, work item changes, and builds. Now anyone can subscribe to just about any work item or build or check-in event in the system - without having to resort to using the bissubscribe.exe command-line tool. After installing it, you get a new Alerts node in the Team Explorer:

You can create all kinds of Alerts. Here’s one I’ve created to alert me when someone else (other than me) checks code into one of our international projects:

And here's an alert that lets me monitor whenever one of my coworkers checks anything in!! :)

When you create a new Alert, you can start from a blank one or pick from a few templates:

Here's another alert I created... lets me know whenever a "QA Issue" gets assigned to me:

You can also right-click on a source code item (file or folder), or work item, and select "Alert on change...". Like this:

Work Item Templates

I love this one!! Allows you to select any existing work item, select "Capture Template..." - which copies existing values into a Template, then apply that template to other new items. Like this:

Selecting "Capture Template..." pops this dialog:

So you can select which fields you want to copy to the template. In this example, I've deselected the last two fields. Then give it a name, and click Save.

Then you can create new work items from this template!!

You can also apply a template to a list of selected work items. So maybe you have a template called "Assign to Canada Development". In that template, you just have only two fields defined: Development Office and Assigned To, with values "Canada" and <blank>. Then you can select a bunch of work items from a query result, right-click, and select "Apply Template...":

The net effect is that all the selected work items would have their Development Office value set to "Canada", and the Assigned To values set to <blank>. Very cool!!!

Source Control Explorer "source location" is now editable - just like Windows Explorer

You can now select the server path in the Source Control Explorer (SCE) and copy-paste it. Further, you can type a server path in the text box, hit enter, and the SCE will jump to that folder.

Source Control Explorer "Local Path" label is now a link

Clicking on the link will open Windows Explorer to the location on your local hard drive.

Right-click and Cloak

Now you can right-click on any folder in the SCE and select "Cloak...":

This makes it soooo much easier to prevent those damn Help files from getting downloaded!!

Auto-check-out for ALL files opened in SCE

Ever open a file within the SCE, edit it, then go to Save the file and the thing is still read-only?!?! No more!! Now the SCE will automatically check-out any file that is opened in the SCE - not just VS solution and project items anymore. This is great for things like Word docs, database scripts, BAT files, etc.

Find in Source Control

From within the SCE, you can now find files by:

Check-out status
File name or wildcard
Changeset

Here's a screen shot:

TFPT unshelve /migrate

This is incredibly cool!! One of the things I've always wanted to do with shelvesets is MOVE them to another branch. I work at an ISV, and we maintain many release and feature level branches. And occasionally someone will start work on a branch, only to be told later that the PMs have changed the target release for the bug fix or enhancement. This is new option allows you to enter a source and target branch, and effectively unshelve changes from one branch to another.

Annoying SCE refresh bug fixed

One last thing… that little bug in the 2005 Team Explorer that sometimes forced a refresh of the ENTIRE source tree when checking out or in from the SCE has been fixed. This drove me nuts – especially when working remotely.

Missing changeset <-> build associations

Jamie Kurtz — Thu, 24 Jul 2008 17:07:56 GMT

This really bit me recently, so I want to point it out. You can read Martin Woodward's post here: http://planetscm.org/user/22/tag/tfs%20top%20tip/, but I've copied the jist of it below.

Basically, TFS 2008 will not associate any changesets to the first build for a Build Definition. This means that if you create your branch, then create a corresponding Build Definition, then make a bunch of changes to the branch (i.e. the changesets) BEFORE running your first build, all those changesets will never be associated with any builds. Ouch!!

The reasoning for this behavior actually makes sense, as described by Martin in the link above:

The reason why Team Build 2008 works in this way is that when Team Build successfully completes a build it stores the label applied to that last good build. The next time it runs a build that is successful it will compare the two labels to detect which changesets were included in the build. It will then look over those changesets for any associated work items and update them to include the build number in which they were fixed.

So of course be careful when upgrading from 2005 to 2008, as you should baseline all your existing builds BEFORE making any changes to the code. If you don't, that link between your changesets and the first builds will be lost forever :(

I agree with Martin, though, that as a matter of best practice you should always run a build from a new build definition prior to starting work on the associated branch.

Some Getting-Started TFS references

Jamie Kurtz — Thu, 12 Jun 2008 14:06:40 GMT

How to implement IT governance such as Sarbanes-Oxley
How to work with mixed environments (including Java and .NET)
How to set up the product for large distributed environments
How and why to take multiple lifecycles into consideration when deploying and using Team System
How to create custom development tools and administer and customize work items
How to monitor your team project metrics using SQL Server Reporting Services

http://www.amazon.com/Visual-Studio-Team-System-Development/dp/0321418506/ref=pd_bbs_sr_2?ie=UTF8&s=books&qid=1212692014&sr=8-2

Using VSTS to support the transition to Agile values and techniques
Forming Agile teams and building effective process frameworks
Leveraging Team Foundation Version Control to help teams manage change and share their code effectively
Implementing incremental builds and integration with Team Foundation Build
Making the most of VSTS tools for Test-Driven Development and refactoring
Bringing agility into software modeling and using patterns to model solutions more effectively
Using the FIT integrated testing framework to make sure customers are getting what they need
Estimating, prioritizing, and planning Agile projects

http://www.amazon.com/Software-Engineering-Microsoft-Visual-Development/dp/0321278720/ref=pd_bbs_sr_3?ie=UTF8&s=books&qid=1212692014&sr=8-3

The role of the value-up paradigm (versus work-down) in the software development lifecycle, and the meanings and importance of “flow”
The use of MSF for Agile Software Development and MSF for CMMI Process Improvement
Work items for planning and managing backlog in VSTS
Multidimensional, daily metrics to maintain project flow and enable estimation
Creating requirements using personas and scenarios
Project management with iterations, trustworthy transparency, and friction-free metrics
Architectural design using a value-up view, service-oriented architecture, constraints, and qualities of service
Development with unit tests, code coverage, profiling, and build automation
Testing for customer value with scenarios, qualities of service, configurations, data, exploration, and metrics
Effective bug reporting and bug assessment
Troubleshooting a project: recognizing and correcting common pitfalls and antipatterns

http://www.codeplex.com/TFSGuide (available as a free PDF download)

Small gotcha in "tf status" Team Foundation Server command

Jamie Kurtz — Tue, 10 Jun 2008 18:49:37 GMT

Today I was trying to find out who has what checked out from a certain folder in TFS - call it $/Project/Folder. I happened to not have most of that folder downloaded yet - i.e. not in my workspace. I went to the command line, and typed the following:

tf status c:\Project\Folder /recursive /user:*

That returned with “There are no pending changes.” – which is interesting because I can see that there ARE pending changes. And yes, my workspace mapping / working folders are configured properly. So then I tried this instead:

tf status $/Project/Folder /recursive /user:*

And that showed all the actual pending changes.

So I guess the moral of the story is that you need to watch out using local paths – as it seemed be answering the question “what are all the pending changes for only the files I have in my workspace?”. Coincidentally, one of the guys on my team mentioned to me the other day that he generally uses server paths when using the tf command-line tool.

TFS Excel integration fails with error TF80076 - after installing 2008 Team Explorer

Jamie Kurtz — Sat, 07 Jun 2008 15:51:56 GMT

I recently discovered that after you install the 2008 Team Explorer (here) - and you already had the 2005 Team Explorer installed - you may not able to view or edit TFS work items in Excel. Instead, you get an error that says: "TF80076: The data in the work item is not valid or you do not have permissions to modify the data. Please correct the problem and retry."

This error is caused when two different versions of the TFS Office Integration plug-in are installed but not configured properly. More details of the problem and a work around can be found here. However, the instructions for configuring your machine to use the 2008 add-in aren't correct. I've posted the correct details below. Make sure you close all instances of Visual Studio prior to following these steps.

To use the Visual Studio 2008 Team Explorer add-in

1. At the command prompt, change directories to:
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

2. Unregister the Visual Studio 2005 Team Explorer add-in by running the following command:
regsvr32 /u TFSOfficeAdd-in.dll

3. At the command prompt, change directories to:
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\

4. Register the Visual Studio 2008 Team Explorer add-in by running the following command:
regsvr32 TFSOfficeAdd-in.dll

Another great tool from Mark Russinovich

Jamie Kurtz — Wed, 14 May 2008 19:19:53 GMT

ZoomIt

http://technet.microsoft.com/en-us/sysinternals/bb897434.aspx

Very nice tool for screen zoom and annotation for use during presentations. I find this particularly useful when collaborating with remote workers via WebEx or iLinc or whatever.

April 2008 Rosario VPC images available

Jamie Kurtz — Fri, 11 Apr 2008 01:10:30 GMT

This seems to be CTP12: http://www.microsoft.com/downloads/details.aspx?FamilyID=65D0E3BD-9DF3-421A-804F-8F01BD90F0B4&displaylang=en

And here's the Free Download Manager list:

http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part01.exe
http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part02.rar
http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part03.rar
http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part04.rar
http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part05.rar
http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part06.rar
http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part07.rar
http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part08.rar
http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part09.rar
http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part10.rar
http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part11.rar
http://download.microsoft.com/download/b/f/9/bf9c1b30-ca2d-4381-8e9e-8b5db9701437/Apr2008RosarioCTP%20_12PartsTotal.part12.rar

ADO.NET Entity Framework (BETA 3) - Hooking SaveChanges()

Jamie Kurtz — Tue, 26 Feb 2008 03:37:46 GMT

I've been looking quite a bit at the new ADO.NET Entity Framework. I'm really hoping to be able to implement the technology to replace our data access layer with all of its generated database and .NET code.

One of the first things I found myself trying to figure out was updating a DateLastMaint field whenever a change is persisted by the ObjectContext. Our applications use this field religiously, and its update needs to be baked down into the architecture so the application developers don't need to mess with it.

In addition to updating fields on entities, we also need to be support auditing. I'm not sure if this little trick would solve that problem, but it's a start. So here's how I did...

I created a ModelFactory class that serves up EDM models that are pre-hooked to update this DateLastMaint field upon saving. Here's the code for the class:

public static class ModelFactory { public static T CreateModel<T>() where T: ObjectContext { T model = Activator.CreateInstance<T>(); model.SavingChanges += new EventHandler(model_SavingChanges); return model; } static void model_SavingChanges(object sender, EventArgs e) { ObjectContext context = (ObjectContext)sender; IEnumerable<ObjectStateEntry> changes = context.ObjectStateManager.GetObjectStateEntries(EntityState.Modified); foreach (ObjectStateEntry entry in changes) { DateTime dateLastMaint = DateTime.Now; int ordinal = entry.CurrentValues.GetOrdinal("DateLastMaint"); entry.CurrentValues.SetDateTime(ordinal, dateLastMaint); } } }

Then to use the ModelFactory class, just do the following:

MyEntities context = ModelFactory.CreateModel<MyEntities>()

One thing to work out yet: The ObjectContext / model should be instantiated within a using block. But doing so caused the underlying connection to get disposed, so my little test app couldn't persist the changes back to the database. Not sure yet how to recreate an instance of the model and have existing changes merged with it???

TFS Process Template Editor

Jamie Kurtz — Thu, 24 Jan 2008 17:06:58 GMT

As a follow-up to the TFS Work Item Tracking presentation I gave last night at IndyTFS, I want to provide some tips for getting started with editing work item types in TFS.

First and foremost, make sure you have downloaded and installed the latest Team Foundation Power Tools. The Process Template Editor is included in that tool set. The downloads and instructions for TFS 2005 are slightly different from those of TFS 2008. So I'll cover those separately below.

Version 2005

To download and install the Power Tools:

1. Download the 2005 Power Tools here. Note that you first need to install the DSL tools redistributable; just look further down on the page for its download

2. Install the DSL tools redistributable first, then the Power Tools itself

Once the Power Tools are installed:

1. Open the TFS client (i.e. Visual Studio 2005)

2. Make sure you have the Team Explorer window showing and a Team Project selected

3. Select Process Editor from the Team menu

4. Select Work Item Types -> Open WIT from Server

5. Enter the name of your TFS server in the dialog that pops up

6. In the next dialog, find and select the Work Item Type you want to edit

7. Click OK

At this point you are ready to edit and save the Work Item Type. Remember that saving it to the TFS server will immediately affect all users using that particular Work Item Type - so be careful!! Read below for some quick pointers on editing the Work Item Type.

Version 2008

To download and install the Power Tools:

1. Download the 2008 Power Tools here

2. Install the Power Tools

Once the Power Tools are installed:

1. Open the TFS client (i.e. Visual Studio 2008)

2. Make sure you have the Team Explorer window showing and a Team Project selected

3. Select Process Editor from the Tools menu (yes, they moved it from the Team menu to the Tools menu in going to 2008)

4. Select Work Item Types -> Open WIT from Server

5. Enter the name of your TFS server in the dialog that pops up (if it pops up)

6. In the next dialog, find and select the Work Item Type you want to edit

7. Click OK

Tips to edit your Work Item Type

This section simply throws out some simple tips for making changes to the Work Item Type. It is important to understand that the Work Item tracking capability within TFS, and the power of using the Process Editor to alter your development workflow, goes far beyond these few tips.

Making a field required - all the time

To make a field required, regardless of state or transition, open the field on the Fields tab. Then click the Rules tab on the Fields Definition dialog. Click the Add button to add a new rule. Then select the REQUIRED rule type. Click Ok. When the dialog pops up that prompts you to enter the "FOR" and "NOT FOR" permissions, just click OK. Click OK again to finish editing the field.

Making a field required - only when transitioning to a certain state

To make a field required when moving from state A to state B, you need to edit the field from within the Workflow designer. So first select the Workflow tab in the Work Item Type editor. Then looking at the visual workflow diagram, find the state on which you want to make a field required. For example, if you want to make the "Assigned To" required when moving a work item from Active to Resolved, find the little blue transition element that has a dot on the Active state, and an arrow on the Resolved state. Right-click on it, and select Open Details. On the dialog tha tpops up, select the Fields tab. If the fields you want to add the REQUIRED rule to is not already in the list, click the Add button. Otherwise, select the field and click the Open button. On the first tab of the Field Reference dialog, select your desired field from the dropdown. Then click the Rules tab, and click the Add button. This will pop the dialog allowing you to select your desired rule - in this example, the REQUIRED rule. Click Ok a few times, and now your field is required only in the given transition.

Adding dropdown list options to a field

Sometimes you have a text field, and you want to provide a list of options to the user. So, assuming you already have a text field on which you want to add or update a list, select the field form the Fields tab and click the open button. Then click on the Rules tab. Click the Add button. This time, instead of REQUIRED, we're going to select the ALLOWEDVALUES rule. After clicking OK, you are presented with a dialog that allows you to enter a list of strings for the dropdown options. Use the Add button, entering the option value and clicking OK, as many times as needed. Then click OK a few times. Your field will now be shown with a dropdown list of options.

More Information

To really learn how to edit Work Item Types, and also how to edit and create your own complete process templates, read the PEUserGuide Word document found in the "C:\Program Files\Microsoft Team Foundation Server Power Tools\Process Template Editor" after you install the 2005 Power Tools, and "C:\Program Files\Microsoft Team Foundation Server 2008 Power Tools\Process Template Editor" after you install the 2008 version of the Power Tools.

You can also find lots of information on utilizing the TFS Process Templates here. This site does a great job covering all the facets of implementing TFS Process Templates, and using the Power Tools to help you along the way. You will also find links to other process templates in the community - some free, and some not.

TFS Power Tools for VS2008!!

Jamie Kurtz — Sat, 05 Jan 2008 00:40:07 GMT

Microsoft just announced (well, back on 12/21) that the Power Tools have been updated and enhanced for Visual Studio 2008.

Here's a quick list of the highlights:

"Find in Source Control" - right-click option to search in source by status, filename, and changeset
"Open in Windows Explorer" - right-click option to open a location in Windows Explorer
The ability to completely destroy both Work Items and Work Item Types (finally, we can clean up all those test WITs!)
An updated Process Template Editor (including performance improvements and bug fixes)

Here's a link to an announcement: http://blogs.msdn.com/edhintz/archive/2007/12/21/team-foundation-power-tools-for-vs2008-hot-now.aspx.

And here's the download: http://go.microsoft.com/?linkid=8013790.

Of course, don't forget to first grab the 2008 version of the Team Explorer. This must be installed prior to installing the new 2008 Power Tools.

ADO.NET Entity Framework Beta 3 Released!!!

Jamie Kurtz — Fri, 07 Dec 2007 18:50:56 GMT

You can now download a version of the ADO.NET Entity Framework that works with VS 2008 RTM: http://www.microsoft.com/downloads/details.aspx?FamilyId=15DB9989-1621-444D-9B18-D1A04A21B519&displaylang=en

And don't miss this little note: "Be sure to download the Entity Framework Tools December 2007 CTP as well for integration with Visual Studio 2008."