Open drwharris opened 2 years ago
The generation of the code-behind file is done at compile time and not via the VS Extension anymore (since years).
Could you post your NuGet package list of the project?
Here you go
Top-level Package Requested Resolved
Azure.Storage.Blobs 12.14.1 12.14.1
FluentAssertions 6.5.1 6.5.1
Microsoft.AspNetCore.Razor 2.2.0 2.2.0
Microsoft.Extensions.Caching.Abstractions 6.0.0 6.0.0
Microsoft.Extensions.Configuration 6.0.0 6.0.0
Microsoft.Extensions.Configuration.Binder 6.0.0 6.0.0
Microsoft.Extensions.Configuration.EnvironmentVariables 6.0.1 6.0.1
Microsoft.Extensions.Configuration.FileExtensions 6.0.0 6.0.0
Microsoft.Extensions.Configuration.Json 6.0.0 6.0.0
Microsoft.Extensions.Configuration.UserSecrets 6.0.1 6.0.1
Microsoft.Extensions.Logging.Abstractions 6.0.0 6.0.0
Microsoft.Extensions.Options 6.0.0 6.0.0
Microsoft.IdentityModel.Clients.ActiveDirectory 5.2.9 5.2.9
Microsoft.NET.Test.Sdk 17.1.0 17.1.0
NUnit 3.13.2 3.13.2
RestSharp 106.15.0 106.15.0
SixLabors.ImageSharp 1.0.4 1.0.4
SpecFlow.NUnit 3.9.52 3.9.52
SpecFlow.NUnit.Runners 3.9.52 3.9.52
SpecFlow.Plus.LivingDocPlugin 3.9.57 3.9.57
@SabotageAndi Any more info on this?
Used Visual Studio
Visual Studio 2022
Are the latest Visual Studio updates installed?
Yes
SpecFlow Section in app.config or content of specflow.json
{ "generator": { "allowDebugGeneratedFiles": true } }
Issue Description
I am continuously getting auto generated changes in my feature files such as
FROM private static string[] featureTags = new string[] { "ignore"};
TO private string[] _featureTags = new string[] { "ignore"};
FROM TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Features", "Get list of Forms avaiable for submit", null, ProgrammingLanguage.CSharp, featureTags);
TO TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Features", "Get a submission", null, ProgrammingLanguage.CSharp, new string[] {"ignore"});
I suspect this might be an issue with another developer having an older version of the extension but not sure.
Steps to Reproduce
Link to Repository Project
No response