Support for Universal Windows Applications (Windows 10)
Scenario: use PostSharp in an Windows Universal Application
Support for UWP was withdrawn in PostSharp 5.0 because of lack of demand.
To my better understanding, P# already supports .NET Core: https://postsharp.uservoice.com/forums/4949-feature-requests/suggestions/9748500-support-for-coreclr-as-a-runtime-platform-includi
Still, you state P# doesn't support UWP yet.
But UWP is (based on) .NET Core.
So, what exactly is not supported by P# in UWP?
Anthony L'Huede commented
Please look into adding this, UWP is annoying enough let alone being restricted from using the best controls and libraries like PostSharp.
If entities like PostSharp don't distribute to UWP it will never be picked up on a large scale by developers who enjoy being efficient and rapid development. WPF and Silverlight are gone to the wind.
FWIW, we have moved on from the Windows Platform and no longer have any stakes in this request...
Correct. But does that mean that PostSharp will not work at 4.4 with applications deployed to the Windows Store?
In my understanding, .NET Native is only required when you deploy to Windows Store.
what does it mean "we removed the .NET Native for the feature". Aren't all store apps .NET Native now?
Dirk Pass commented
How can an "Internet of things device" be supported by aspects? If the answer was "In multiple ways" I couldn't see any special requirement for IoT.
Support for IoT devices
Alistair “Cerebrate” Young commented
This is the major hold-up in my current development project. Working without my library of custom PostSharp aspects is _painful_ !