Closed Konnor5092 closed 5 years ago
You have left passwords in the pasted app.config!!!! Please remove them and change them! There are crawlers that search GitHub for those. You have to see them as compromised!!
From: Konnor5092 notifications@github.com Sent: Friday, May 10, 2019 12:41:38 PM To: techtalk/SpecFlow Cc: Subscribed Subject: [techtalk/SpecFlow] MSBuild codebehind generation is not working during an Azure Devops build only (#1562)
SpecFlow Version:
Used Test Runner
Version number: 3.0.337
Visual Studio Version
Are the latest Visual Studio updates installed?
.NET Framework:
= .NET 4.5
Test Execution Method:
Oops. Edited and removed. Ta
The .feature.cs code-behind files are generated by the SpecFlow.Tools.MsBuild.Generation
NuGet package, so it is good that they are there. So I am not sure where you have a issue.
Should the code behind files be visible in the solution explorer? They aren't for me...
I tried deleting all the .feature.cs files locally, rebuilding locally and they were all regenerated. Builds fine. They aren't flagged as pending changes though. Is that to be expected?
Somehow something has got out of sync, but I don't know how or where.
This is sorted. Issue was due to a rogue feature file I hadn't updated in an unloaded project.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
SpecFlow Version:
Used Test Runner
Version number: 3.0.337
Visual Studio Version
Are the latest Visual Studio updates installed?
.NET Framework:
Test Execution Method:
<SpecFlow> Section in app.config or content of specflow.json
Repro Project
Issue Description
Hi there,
Since upgrading to SpecFlow 3 I’ve had lots of issues trying to get a build to run as part of a gated check in. The error that keeps getting returned is...
My project builds and runs locally, after getting latest. This error is specific to running builds in Azure Devops.
As per the documentation I have removed ‘SpecFlowSingleFileGenerator’ from every feature file, including the one mentioned in the error above. As soon as I removed the text, the code behind file appeared to be removed, however it didn’t process the deletion of these files properly when checking into source control, so I had to force a check in bypassing the gated build.
This is what the properties on all of my feature files looks like...
For some reason, the build agent is still generating these files during a build....
Even though these files no longer exist in source control...
Could there be a reference somewhere else that might be causing the error when a build is ran?
I have checked my .csproj file to see if I had any entries as described in this blog post - https://specflow.org/2018/specflow-3-public-preview-now-available/, however there are none, probably because I have not added any feature files since upgrading.
Below is my .csproj file...
Steps to Reproduce