The type 'PermissionSet' exists in both 'System.Runtime.Extensions' and 'System.Security.Permissions'

[danzil]

This is a recent regressions.

I just updated my local WPF repo to use ‘SDK 3.0.100-preview-010024’ and that breaks System.Xaml compilation. The SDK I had previously (3.0.100-preview-009764) works just file.

System\Xaml\Runtime\DynamicMethodRuntime.cs(43,16): error CS0433: The type 'PermissionSet' exists in both 'System.Runtime.Extensions, Version=4.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' and 'System.Security.Permissions, Version=4.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' [Y:\dotnet-wpf-prototype\src\Microsoft.DotNet.Wpf\src\System.Xaml\System.Xaml.csproj]

System\Xaml\Permissions\XamlLoadPermission.cs(20,35): error CS0433: The type 'PermissionState' exists in both 'System.Runtime.Extensions, Version=4.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' and 'System.Security.Permissions, Version=4.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' [Y:\dotnet-wpf-prototype\src\Microsoft.DotNet.Wpf\src\System.Xaml\System.Xaml.csproj]

[danzil]

@rladuca found these similar reports which may be related: #28323 and #28299

[danmoseley]

@joperezr @ericstj could one of you please help figure out the resolution to these linked issues? Beyond my expertise.

[ericstj]

That new SDK will be delivering a new System.Runtime.Extensions via the shared framework. We moved types down from S.S.Permissions into S.R.E. We left type-forwards behind so it is binary compatible, but you need to update the reference of S.S.Permissions to the new one so that the compiler knows which typedef to use.

You need to update your System.Security.Permissions reference to be in sync.
https://github.com/dotnet/wpf/blob/39c46e1d69df6d3ad10e60d5f07db3bc5e6c81a7/eng/Versions.props#L7-L8

@stevenbrix @rladuca Any reason why you are using old versions here? I'd expect you to be keeping these in sync with the latest packages out of corefx so that you build/test against what eventually gets packaged into the windowsdesktop shared framework.

[rladuca]

@ericstj This is a better question for @danzil as he is working on the specific repo where this is occurring.

[ericstj]

@rladuca if I understand correctly he's working on http://github.com/dotnet/wpf and the problems I point out above are issues with that repository.

[ericstj]

Closing this issue in favor of this: dotnet/wpf#248.

[danzil]

Thanks for looking at this @ericstj - I'll look at the package versions we use there