Andrew Boyarshin

Encountered the bug too. Easy to reproduce by rotating the screen.

@whilu yes, I release instance. I tried it many ways, now I just implemented most Activity lifecycle callbacks (onDestroy, onPause etc) and I call super implementation in `try {...} catch...

I can help you debug it if you provide the repro. Without it I can only recommend checking that there are references to the instance of the class that implements...

AFAIR, before beta.11 SharpGen was storing a strong reference to the implementation instance in the `CppObjectShadow` instance (`Callback` property) while creating a strong GCHandle to itself. Now it doesn't (it...

@Steph55 I'm not sure if moving the reference storage semantics to Vortice is the right way forward. If done for D2D effects, it can be surprising that some other callback...

@amerkoleci what about the lifecycle concerns? Isn't this exactly what I said is a bad idea? Okay, imagine you did it for CustomEffect, what about other callback interface implementations? Why...

The 2019 `csproj` is _almost_ the 2017 `csproj`. I doubt any tool exists that will enable backwards compatibility between CPS project formats. Is there a particular issue that you face...

I guess you are trying to open .NET Core 3.0+ Windows Forms/WPF solutions using VS2017. VS2017 supports a maximum of .NET Core 2.2 SDK. I suggest you use VS2019 Community...

Yeah, `ComVisible` is still true by default in CPS I'm afraid. It's a known bad practice and even VS sets it to false by default in AssemblyInfo on project generation....

@moh-hassan thank you for your report. If I understood you correctly, both of these features are already implemented in this tool. Are they not working correctly? If so, could you...