SpecFlow and SharePoint

[Craig]

Hi,

Has anyone tried to run SpecFlow.NET together with a SharePoint
project in Visual Studio 2010?

We tried to do it yesterday but we had a problem where both SharePoint
and SpecFlow.NET were using .feature as the file extension. Since
SpecFlow.NET was installed after the SharePoint SDK SpecFlow.NET "won"
and we couldn't get the SharePoint project working :-(


Craig

[Gáspár Nagy]

Hi,

I'm sure you know the SharePoint project better then me. Do you see
any conceptual idea how this conflict could be resolved? What parts
are conflicting, the syntax coloring or the generation? Is the
SharePoint ".feature" file can also be placed in a normal c#/vbnet
project?

Tips for manual workarounds:
to switch off the automatic recognition of the .feature file for the
_genrator_:
- rename key ".feature" to ".featureX" at "HKEY_LOCAL_MACHINE\SOFTWARE
\Microsoft\VisualStudio\10.0\Generators\{FAE04EC1-301F-11D3-
BF4B-00C04F79EFBC}\.feature" (this is for C# projects)
- you can still set the generation manually in VS by specifying
"SpecFlowSingleFileGenerator" for the "custom tool" property of the
file

to switch off syntax coloring:
- remove (or rename) the shortcut at C:\Program Files\Microsoft Visual
Studio 10.0\Common7\IDE\Extensions\TechTalk\SpecFlow

Br,
Gaspar