FW: specflow with vs2005
Jonas Bandi
I am forwarding this interesting information to the Group …
From: Gaspar Nagy
Sent: Donnerstag, 17. März 2011 08:53
To: DAVIS, Andrew
Cc: Jonas Bandi; Christian Hassa
Subject: RE: specflow with vs2005
Hi,
I’m almost sure that the basic generator would also work for VS2005. You only need to set a few registry setting. These are the usual settings for VS2008. You can adopt them to VS2005 and your installation path (please note, that these are for x64, if you use x32, you have to remove the Wow6432Node part.
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\9.0\CLSID\{3c9cf10a-a9ab-4899-a0fb-4b3be4a36c15}]
@="TechTalk.SpecFlow.Vs2008Integration.SpecFlowSingleFileGenerator"
"Class"="TechTalk.SpecFlow.Vs2008Integration.SpecFlowSingleFileGenerator"
"CodeBase"="C:\\Program Files (x86)\\TechTalk\\SpecFlow\\TechTalk.SpecFlow.Vs2008Integration.dll"
"InprocServer32"="C:\\\\Windows\\\\SYSTEM32\\\\MSCOREE.DLL"
"ThreadingModel"="Both"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\9.0\Generators\{FAE04EC1-301F-11D3-BF4B-00C04F79EFBC}\.feature]
@="SpecFlowSingleFileGenerator"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\9.0\Generators\{FAE04EC1-301F-11D3-BF4B-00C04F79EFBC}\SpecFlowSingleFileGenerator]
@="C# SpecFlow Generator"
"CLSID"="{3c9cf10a-a9ab-4899-a0fb-4b3be4a36c15}"
"GeneratesDesignTimeSource"=dword:00000001
You can also use SpecFlow without VS integration, through an MsBuild task. You can read about this in the user’s guide draft.
Br,
Gáspár
From: DAVIS, Andrew
Sent: Wednesday, March 16, 2011 5:52 PM
To: Specflow Info
Subject: specflow with vs2005
Hi,
is there a way to make specflow work with visual studio 2005? This is for use with Biztalk 2006 (for which development occurs in vs2005)
Many thanks
Andy.
Michael stephenson
I tried to do this but had some issues:
1. The msbuild task didnt seem to work as has dependancies on msbuild
3.5 which i dont think you can use from vs2005
2. I called specflow.exe using the msbuild command task which works
great except that the generated code has some dependancies on C#3.0
features which means the generated code does not compile.
I assume the same will happen if you use the above modified registry
snippets