Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

csproj files checked out when running unit tests #538

Unanswered
ExaxeDevelopment asked this question in Q&A
Discussion options

Since starting to use FinCodeCoverage either all csproj files, or all the unit test csproj files get checked out when we run tests.
Is this necessary? Can we stop it?

Thanks

You must be logged in to vote

Replies: 1 comment 4 replies

Comment options

What version of FCC and Visual Studio are you using ?
This used to be an issue and I thought that it had been resolved.

Is this necessary?

When RunMsCodeCoverage Yes and you do not supply your own .runsettings file FCC must write to the .csproj. We then remove it at the end.

private readonly IVsRunSettingsWriter vsRunSettingsWriter;

https://github.com/FortuneN/FineCodeCoverage/blob/master/SharedProject/Core/MsTestPlatform/CodeCoverage/VsRunSettingsWriter.cs
https://github.com/FortuneN/FineCodeCoverage/blob/master/SharedProject/Core/Utilities/ProjectFilePropertyWriter.cs#L9

Can we stop it?

Yes.

Provide your own runsettings - https://learn.microsoft.com/en-us/visualstudio/test/configure-unit-tests-by-using-a-dot-runsettings-file?view=vs-2022
Or
RunMsCodeCoverage No. - there is different behaviour though. Tests run then all tests run again but under a different location.

You must be logged in to vote
4 replies
Comment options

FCC v1.1.245
VS 2022 professional v17.14.16

We do not provide a runsettings file. I will add one and see what effect that has.

Comment options

adding a .runsettings file did the trick. My question has been answered.

Do you want any more information about the checking files out issue that you thought might be fixed?

Comment options

Do you want any more information about the checking files out issue that you thought might be fixed?

Yes please. Does it happen all the time ? On particular projects ?

Comment options

For me it checked out every project on every solution I ran unit tests on most of the time. Occasionally it would just check out the unit tests project files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

AltStyle によって変換されたページ (->オリジナル) /