Skip to content
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

Adding option to disable shadow copy (consistent with command line runne... #9

Closed
wants to merge 1 commit into from

Conversation

tulebast
Copy link

...r /noshadow option).

I am using the negative DisableShadowCopy rather than the more positive EnableShadowCopy to mirror the negative /noshadow option of the command line runner.

@tulebast
Copy link
Author

I was not sure if I needed to bump the version number or not (I apologize for being pressed for time, I couldn't find a contributors' guide so I did it just to be safe). The lack of this option was causing a problem with users who were coordinating tests across several diverse environments. Ultimately, automated test suites run by a build process use the command line runner with the /noshadow option. Test writers using the Resharper plugin setting to disable shadow copy are fine, but those not using the Resharper plugin are unable to load existing tests and run them with correct behavior because of the forcing of shadow copy. [For reasons beyond this post, liberal use of DeployItem attribute is not available.]

@Tofudebeast
Copy link

Note that I have the same option exposed in my pull request. I also expose the config file option.

@exalted
Copy link

exalted commented Sep 1, 2014

👍

@bradwilson
Copy link
Member

This will break the Visual Studio runner functionality, so we will not be taking this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants