Please clarify: How to separate Nuget tags in project file?

[SetTrend]

The .nuspec File Reference for NuGet reads:

tags

A space-delimited list of tags

The Visual Studio 2022 project file designer reads:

Semicolon or space delimited? What's correct?

[nkolev92]

Since tags don't accept spaces, it doesn't really matter.

tag1;tag2 becomes tag1 tag2 in the nuspec
tag1 tag2 becomes tag1 tag2 in the nuspec
tag1; tag2 tag3 becomes tag1 tag2 tag3 in the nuspec
tag1 tag2; tag3 becomes tag1 tag2 tag3 in the nuspec

[SetTrend]

Thank you, @nkolev92, for enlightening me.

It seems the informational label in Visual Studio 2022 doesn't explain that fact.

In fact, I might enter My Export Package; My Import Package in a .NET project file and expect this to create exactly two tags: My Export Package and My Import Package in the NuGet package.

Also, using a "semicolon-delimited list of tags" implies that semicolons are no valid characters for NuGet package tags. Yet, are they?

Shouldn't the information either at learn.microsoft.com/nuspec#tags and/or in the Visual Studio informational label be amended to elaborate on the characters valid for NuGet package tags? E.g. the informational label could claim: "Whitespace is not allowed for any tag or keyword." or "Only … characters allowed for NuGet package tags." (e.g., UNICODE classes Ll, Lt, Lu, Nd, Nl, No …)

[nkolev92]

semicolon is a common delimeter in msbuild world.

I think we can amend the docs and potentially VS to clarify how things work.

Fwiw, I'm not 100% certain if the whitespace restriction is a nuget.org thing or a more general thing.