SpecFlow 1.8.0 released

[Gáspár Nagy]

Today we released SpecFlow 1.8.0

You can download it here:
http://github.com/techtalk/SpecFlow/downloads

Thanks goes to the contributors!
If you have any problems please report it on the official Google
group.

Breaking changes:
+ Classes used for context injection must have a single public
constructor with maximum parameter count (so far the first constructor
was used).
+ After step hook is was not invoked when step definition failed so
far. Now it is invoked even in case of a failure.

New features:
+ Async testing support for Windows Phone 7 (Issue 132, by Jeff
Simons)
+ Support for MbUnit v3. Use unit test provider name "mbunit.3".
(Issue 133, by Raytheon)
+ SpecFlow framework classes can be used as a dependency for context
injection.
+ Custom extensions for the runtime can be specified in the config
file (specflow/runtime/dependencies).
+ Better customization possibilities with plugins.
+ [StepScope] attribute can also scope hooks (event bindings) (Issue
95)
+ [StepScope] has been renamed to [Scope]. [StepScope] is kept with
obsolete warning.
+ VS2010: Run & debug scenarios from the feature file context menu and
solution explorer nodes (feature file, folder, project).
+ VS2010: Use infix word prefix matching for step completion.
+ VS2010: Regenerate feature files from project context menu.
+ VS2010: Go to step definition command in feature file context menu.
+ MsBuild generator can output generated file paths (GeneratedFiles
property). The file list is populated to the MsBuild item
@(SpecFlowGeneratedFiles) by the TechTalk.SpecFlow.targets.
+ MsBuild: TechTalk.SpecFlow.targets provides overrideable
BeforeUpdateFeatureFilesInProject and AfterUpdateFeatureFilesInProject
targets.
+ Cucumber harmonization
+ Allow using [Before]/[After] attributes as synonyms of
[BeforeScenario]/[AfterScenario]
+ Allow using [StepDefinition] attribute that matches to given, when
or then steps
+ Leading '@' sign can be specified for hooks and [Scope] attribute

Fixed issues:
+ Instances created for context injection are disposed after scenario
execution (Issue 22)
+ Error when opening feature file in VS2008 if VS2008 syntax coloring
was enabled.
+ Silverlight: make possible to access SilverlightTest instance (Issue
126, by Matt Ellis)
+ Silverlight: apply feature tags to the test class instead of the
methods (Issue 126, by Matt Ellis)
+ SpecFlowContext.TryGetValue does not evaluate Func<T> factory
methods (Issue 127, by Matt Ellis)
+ StepArgumentTransformation cannot be used recursively
+ VS2010 locks generator folder
+ After step hook is not invoked when step definition failed.
+ Missing XML comment warnings caused by the generated test class
(Issue 121)
+ VS2010: Goto step definition misdiagnoses Given-But as a Then-But
(Issue 134, by Raytheon)
+ VS2010: 'Go To Definition' does not work with partial classes.
(Issue 53, by Raytheon)
+ AfterTestRun-Hook does not trigger when running in NUnitGui or
NUnitConsole. To fix this, you need to add the NUnit addin from
https://raw.github.com/techtalk/SpecFlow/master/Installer/NUnitNuGetPackage/SpecFlowNUnitExtension.cs
to the project, or use
the SpecFlow.NUnit combined NuGet package that does this
automatically.


The complete changelog is here:
https://github.com/techtalk/SpecFlow/blob/master/changelog.txt