You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just noticed that the SyncToAsync.Shared project is non-sdk-style and imports PresentationFramework. Obviously not a bug and makes no difference to the end user, but I was just wondering if this was necessary. SDK-style projects are a lot easier to read and they can produce IL for .NET Framework too.
Same applies to SyncToAsync.Extension.csproj and SyncToAsync.Extension.csproj
The text was updated successfully, but these errors were encountered:
I just noticed that the SyncToAsync.Shared project is non-sdk-style and imports PresentationFramework. Obviously not a bug and makes no difference to the end user, but I was just wondering if this was necessary. SDK-style projects are a lot easier to read and they can produce IL for .NET Framework too.
Same applies to SyncToAsync.Extension.csproj and SyncToAsync.Extension.csproj
The text was updated successfully, but these errors were encountered: