The product codenamed Fidalgo has undergone a name change.   Fidalgo was previously named "Microsoft Visual Studio Code Name “Orcas” Community Technology Preview - Development Tools for .NET Framework 3.0"  and prior to that "Microsoft Visual Studio Code Name “Orcas” Community Technology Preview - Development Tools for WinFX".  We originally made this first change from WinFX to .NET Framework 3.0 because the runtime itself had changed names and it was important for us to match that name change.

With the most recent CTP of Fidalgo we have adjusted the name again.  The new name is "Visual Studio 2005 extensions for .NET Framework 3.0 (WCF & WPF), November 2006 CTP".

 Many questions probably come from this.  Let me answer a few of them:

Q:Why did we change the name?
A:We chose the original name because we wanted to communicate to customers that this CTP of ..NETFX3 development tools would be fully available in the next Version of Visual Studio.  As the next version of VS started releasing its own CTPs we realized the confusion this would create.  This didn't change our charter that customers will be expected to upgrade to Orcas when it ships but we could at least make things easier for the time you do use Fidalgo. 

Q:What is the difference between Fidalgo and the WF extensions for VS 2005?
A:Fidalgo only focuses on WCF & WPF.  It does not have any features to work with WF.  The WF extensions focus exclusively on WF.

Q:Why did Fidalgo go from Development tools for .NET Framework 3.0 to .NET Framework 3.0 (WCF & WPF)?
A:Fidalgo always only focused on the WCF & WPF technologies of the .NET FX 3.  We just didn't spell it out in the name because it was already long enough.  With the new name we felt it was important to distinguish this from the WF extensions for VS 2005 which focus on on WF.

Q:Why do the name change now?
A:This is the last release of the Fidalgo CTP.  Any future technology improvements will appear in the next release of Visual Studio which is codenamed Orcas.  We wouldn't get another chance to clarify this in the future as more customers began using Fidalgo.

I hope this helps address some of the questions around why we went with this name change and I hope it makes it easier to understand what role Fidalgo serves for you.