> the strange thing is, that when I did this simplification, I was sure
> that nobody uses partial classes as bindings. assumptions are always
> dangerous... :)
> not in 1.6, but I'll fix it. could you register an issue for this
> please?
> On Mar 30, 3:43 pm, Jason Evans <testms...@hotmail.com> wrote:
> > Hi there.
> > Ahhh, yes, your right.
> > I have my steps split into 3 separate files:
> > - StepsGiven.cs
> > - StepsWhen.cs
> > - StepsThen.cs
> > I use one partial class defined across those three files, but only
> > StepsGiven has the [Binding] attribute.
> > StepsGiven.cs:
> > [Binding]
> > public partial class Steps : BaseTest { //
> > StepsThen.cs:
> > public partial class Steps { //
> > So I guess my splitting of the class is causing a problem with the 'Go
> > To Definition'. It works fine for steps found in the StepsGiven.cs
> > file, but not if the steps are stored in either of the other two
> > files.
> > Cheers.
> > Jas.
> > On Mar 30, 1:07 pm, Gáspár Nagy <gaspar.n...@gmail.com> wrote:
> > > I did a quick test and it worked for me, so my questions are:
> > > - Is it possible that you had some [StepScope] on the class?
> > > - Was the project in a compilable state?
> > > - Do you have the [Binding] attribute on the same file as the step
> > > binding?
> > > - Could you make a small repro project?
> > > On Mar 30, 9:56 am, Gáspár Nagy <gaspar.n...@gmail.com> wrote:
> > > > No. Theoretically this should work. I'll check.
> > > > On Mar 29, 5:38 pm, Jason Evans <testms...@hotmail.com> wrote:
> > > > > Hi there.
> > > > > Using version 1.3.5.33 of the VS 2010 features MSI. I spotted
> > > > > something that I'm unsure how easy it would be to resolve.
> > > > > When I right-click on the following line in a feature file:
> > > > > Then the webpage will contain the text "Daily Community Spotlight"
> > > > > and choose 'Go To 'Definition' I get a message saying:
> > > > > 'No matching binding found for this step'
> > > > > Here is the step:
> > > > > [Then(@"the webpage will contain the text ""(.*)""")]
> > > > > public void ThenTheWebpageWillContaingTheText(string text)
> > > > > {
> > > > > Assert.IsTrue(ActiveBrowser.ContainsText(text), "Webpage did not
> > > > > contain expected text.");
> > > > > }
> > > > > I think that because the method name is generic (in other words, we're
> > > > > using (.*) to capture the text), it seems that SpecFlow is unable to
> > > > > match the feature file 'Then' to it's step binding.
> > > > > Cheers.
> > > > > Jas.
