Reqnroll
Ignore *.feature.cs files in our .gitignore #1026
-
|
Should we add *.feature.cs to our .gitignore file? I can see that you have in this Solution, but can't see any recommendation to do so anywhere else. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Most teams adopt the practice of NOT committing the generated code-behind files (*.feature.cs) to their source control. Until quite recently this was accomplished by the use of an entry in the .gitignore file. With Release 3.3.0, you also have the option of setting an MSBUILD property that will cause Reqnroll to place the generated code files into the intermediate output folder (obj folder). Set the |
Beta Was this translation helpful? Give feedback.
-
|
In general it's not recommended to add generated code to version control/git. So git ignore is a good idea :) |
Beta Was this translation helpful? Give feedback.
Most teams adopt the practice of NOT committing the generated code-behind files (*.feature.cs) to their source control.
Until quite recently this was accomplished by the use of an entry in the .gitignore file.
With Release 3.3.0, you also have the option of setting an MSBUILD property that will cause Reqnroll to place the generated code files into the intermediate output folder (obj folder). Set the
ReqnrollUseIntermediateOutputPathForCodeBehindMSBuild property to true; see description of the PR.