部分SpecFlow特性文件生成名称含1的原因及相关技术问题咨询

Great question—this is a common pain point with SpecFlow's Visual Studio integration vs. command-line generation. Let's break down what's going on and how to fix it:

The "1" suffix on your generated .feature.cs files almost always comes down to naming conflicts or leftover cached generation data:

• You might have two .feature files that would generate the same class name (by default, SpecFlow uses the feature filename for the generated class). Even if they're in different folders, if your namespace configuration leads to duplicate fully qualified class names, SpecFlow appends "1" to avoid collisions.
• Sometimes old generated files aren't properly cleaned up. When you run "Regenerate Feature Files" or "Run Custom Tool", Visual Studio's generator detects an existing file with the same name and adds the suffix to prevent overwriting.
• Double-check the Custom Tool Namespace property of the problematic .feature files (right-click → Properties). If multiple files share the same namespace and filename, this will trigger the duplicate class name issue.

The VS integration and generateall command-line tool work independently, which causes these discrepancies:

• Nested file display: VS shows .feature.cs files nested under .feature files because the project file (.csproj) includes <DependentUpon> nodes linking them. The generateall command doesn't modify your .csproj, so generated files appear as standalone items in Solution Explorer.
• Test Explorer not finding tests: There are a few likely culprits here:
  • The generated .cs files aren't included in your project. VS's test discovery only scans files that are part of the project, not loose files in the directory.
  • The command-line generation is using a different configuration than VS. For example, if you're using xUnit in VS but generateall defaults to NUnit, the test framework attributes won't match, and tests won't show up.
  • Compilation errors in the generated code can block test discovery—check the Error List in VS for issues with the command-line-generated files.

Let's resolve these issues one by one:

1. Clean up conflicting files

   • Delete all .feature.cs files with "1" in the name, plus any standalone .cs files generated by generateall. Only leave your original .feature files in the project.
   • Audit all .feature filenames to ensure no duplicates (even across folders) that would lead to identical class names.

2. Fix VS generation issues

   • Right-click a problematic .feature file, go to Properties, and confirm the Custom Tool is set to SpecFlowSingleFileGenerator.
   • Verify the Custom Tool Namespace is unique per file (or structured to avoid duplicates, e.g., using folder names as part of the namespace).
   • Run "Clean Solution" (Build → Clean Solution), then "Rebuild Solution" to clear any cached generation data.

3. Align command-line generation with VS

   • When using generateall, use the --test-framework parameter to match your VS test framework (e.g., specflow generateall --test-framework xunit).
   • Use the --output-dir parameter to generate files in the same directory as your .feature files (e.g., specflow generateall --output-dir .).
   • After generating, manually add the .feature.cs files to your project (right-click project → Add → Existing Item) to get them recognized by Test Explorer.

4. Clear SpecFlow/VS cache

   • Close Visual Studio, delete your project's obj and bin folders, then reopen VS. This clears leftover cached generation artifacts that might be causing odd behavior.

内容的提问来源于stack exchange，提问作者stuartdotnet