Test projects end up with this GUID

[davidfowl]

Is there any way to get rid of this GUID? Can it come from somewhere else? The SDK? Maybe? A nuget package? Why does this exist? Who it for? Can it be inferred?

<ItemGroup>
    <Service Include="{82a7f48d-3b50-4b1e-b82e-3ada8210c358}" />
  </ItemGroup>

[smadala]

VS generates this automatically, to identify project as test project. More details here.

[davidfowl]

Can we make test projects have their own msbuild sdk to avoid this being added to all test projects?

[codito]

#440 is adding a capability for test projects. This guid dependency should go away once VS Test Window starts consuming this.

[davidfowl]

Is that an RTM feature? I'd love to keep the project files as clean as possible...

[codito]

Not planned for RTM currently.

Tagging @sbaid @pvlakshm @srivatsn for bar check.

[codito]

Triage: this will require a fix in test window, we should take this in 15.1.

[davidfowl]

My project file thanks you.

[jnm2]

This kind of noise going back and forth in your source control is a bit irritating, when a bunch of project files suddenly have pending changes and nothing of real consequence happened. I'm really looking forward to getting it out of there.

[NickCraver]

I'm on 15.1 and this is still annoying the crap out of me on every commit trying to sneak its way into my git repo. What's the status of removing this thing?

[JamesNK]

Conscientious csproj citizens don't dirty pristine projects with their grubby GUIDs.

[navin22]

This issue is fixed. Fix will be available in the next VS update.

[PureKrome]

Thank you heaps!

[jnm2]

This issue is fixed. Fix will be available in the next VS update.

Wow so that was quick! Is this the version you're referring to or is it the next one?
https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#a-id1522643004arelease-date-may-10-2017---version-152-2643004

[codito]

This fix should be part of the next 15.3 preview updates.

[sharwell]

@navin22 @codito I just hit this in 3 projects with Visual Studio 2017 version 15.3 Preview 6.

[navin22]

@sharwell Does the project have the "TestContainer" Capability?
<ProjectCapability Include="TestContainer" />

BTW, If the service GUID is already added, the fix made can't remove it. It should be removed manually.

[sharwell]

Does the project have the "TestContainer" Capability?

I'm assuming you are referring to the UnitTestContainer capability.

I'm not sure. It is possible the bug is currently only affecting cases where this capability is not included. However, it would still be the same bug for these cases. If separate test-related handling is desired for projects which do not have this capability, it needs to be relocated to either the solution user options (*.suo) or the project user options (*.csproj.user).

BTW, If the service GUID is already added, the fix made can't remove it. It should be removed manually.

Yes, this is my expectation.

[jnm2]

If separate test-related handling is desired for projects which do not have this capability, it needs to be relocated to either the solution user options (.suo) or the project user options (.csproj.user).

Absolutely.

[wilhen01]

Just updated to 15.6 and suddenly seeing this in all our NUnit .csproj files. Yuk.

[wilhen01]

@smadala or someone else from MS, can we reopen this issue please?

[jnm2]

To reiterate, in case there's a chance: If the presence of this GUID is somehow useful to VS, would you please redirect it into the .vs cache and keep our projects clean?

[ManishJayaswal]

@singhsarab - I don't think this was ever fixed. I have reopened the issue.
@navin22 - let's chat offline to understand why this was resolved as fixed and if was indeed fixed then what change in 15.6 brought it back.
@KevinH-MS - FYI

However the good news is that we have actually fixed this in 15.7 release - this time for sure, I promise :-)

We wanted to make this change early in a release to understand all the fall outs since apparently code lens test indicators had a dependency on it. 15.7 Preview 1 will release shortly and that would have this change. We will close this issue after someone in the community has verified that 15.7 release does fix this.

[HppZ]

still happen in 15.6.2

[mookid8000]

Seems to be an issue in 15.6.4 too .... good times 😐

[jnm2]

@HppZ @mookid8000 Like the team said right above your comments, you should not expect this to work until 15.7.

Has anyone installed 15.7 yet? I'm going to play with Blazor when I get a chance, so if no one else wants to confirm the GUID fix I'll do it.

[davkean]

This has been fixed in 15.7.