-
-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
optional ThisAssembly generation #292
Comments
I would accept a PR for this. Here's a mini-spec of how I would want it: An msbuild property that turns it off. It should be called |
Closing due to a workaround being available or lack of popular demand. This allows us to better focus on high impact issues. If you feel this is blocking you, you may add a comment here to explain why this should be prioritized. Thank you for your understanding. |
Oops. This actually did get fixed in #472 |
I would like to use this feature to suppress ThisAssembly class generation, how can I do? |
Yes |
Bumps [dotnet-coverage](https://github.com/microsoft/codecoverage) from 17.12.4 to 17.12.5. - [Commits](https://github.com/microsoft/codecoverage/commits) --- updated-dependencies: - dependency-name: dotnet-coverage dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Is it possible to (optionally) turn off the generation of the ThisAssembly class?
We had a situation where we hit an issue in combination with Fakes generation that took me a while to figure out. (this was eventually solved by adding
<Remove TypeName="ThisAssembly"/>
in the fakes config).However, I am not sure if anyone has experienced issues where another library actually generates ThisAssembly content that would conflict with this library.
In that case they would also benefit from a 'switch' to turn it off.
The text was updated successfully, but these errors were encountered: