Feature files and binding files do not work from (VS2013 Update 4) shared projects.

[gmurray81]

See title. This is super critical for sharing lots of feature files between multiple unit test projects. (We do this for cross-platform testing).

The issues seem to boil down to:

• Shared projects don't seem to support Custom Tool => Generators
  • Maybe it is possible to have the generators be invoked from the context of the project including the shared items?
  • Maybe it would be appropriate to manage the generators differently? Other than custom tool?
• SpecFlow doesn't register a shared project as something to listen for project item changes for
  • This one seems simple enough to fix.
• Shared projects seem to result in the ProjectRelativePath for a FileInfo to start with a left angle bracket, and there are a few places where Specflow builds a full file path using this that winds up with disallowed characters in the path.

[gmurray81]

Also, probably it won't be able to find the write app.config, I would think. The feature editor should probably be able to bring up the project context switcher combo, too.

[darrencauthon]

If I were to concretize this request a little bit...

1.) You create a Shared Project that contains (a) feature files, and (b) step bindings. 2.) You create another project and reference the Shared Project from (1). 3.) You build the project you created in (2), and SpecFlow does not recognize the (a) feature files and (b) step bindings. SpecFlow does not build the unit tests from (a), so there are no unit tests to run from the project build in (1).

Is that it?

[darrencauthon]

And when you say you do this for cross-platform testing... can you give an example of this?

Like a case where you'd want to share the feature & step definitions across multiple projects?

[gasparnagy]

stared projects (and also linked files) are not supported currently. I fear this is quite a bit of work to fix this...