DiscoverOnlineOrganizationsAsync fails with tokenCacheStorePath when AppDomain.CurrentDomain.FriendlyName has invalid characters

[cupacheeno]

Using the Service Client DiscoverOnlineOrganizationsAsync static method with the optional parameter tokenCacheStorePath will fail when the AppDomain.CurrentDomain.FriendlyName contains invalid characters.

For example.
Microsoft.PowerPlatform.Dataverse.Client = 1.1.14

Visual Studio Project = VSTO Add-In

The call will fail in the Microsoft.PowerPlatform.Dataverse.Client.Auth.TokenCache.FileBackedTokenCacheHints.FileBackedTokenCacheHints method as it attempts to use the AppDomain.CurrentDomain.FriendlyName

Unfortunately this property is not an editable property and as such in this particular instance would be
"Project.vsto|vstolocal" and throw an exception.

[MattB-msft]

We are going fix this as part of 1.1.16 which should be shipping later today.

[MattB-msft]

Fix merged as part of #411

[cupacheeno]

@MattB-msft just checked this however the fix has not been successful.
Taking a look at PR #411
In src/GeneralTools/DataverseClient/Client/Auth/TokenCache/FileBackedTokenCacheHints.cs Line 39
text = Path.GetFileNameWithoutExtension(AppDomain.CurrentDomain.FriendlyName);
It continues to fail here as it is called prior to the fix.

[MattB-msft]

oh. you were saying the .net file handler is failing ... ah. sorry misunderstood you there. will reopen and track this down.

[MattB-msft]

More complete fix added in next drop.