Replies: 1 comment 4 replies
-
This is a great idea for a nuget package (if it does not already exist). I don't think this has to be part of Uno, as it does not touch any part of the Uno features themselves. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Uno is officially not compartiblity to .net Framework e.g 4.8 what I do have to connect to at my job. But I thought about, just because its not at all guaranteed to be working especially in this scenario and then the difficulty has future more been to me, that the application that has been is a COM interop I only got a interop.dll from🫣😅🤷
Was almost giving up, but tryed out this last thing expecting it already do just fail! But... IT WORKS GREAT!
So to enable others to do the same if they need to and futuremore not having to create a own library with this locally, I would love to have this functionality added to the uno capabilities and enhance also its (backwards) compartiblity! 😍
The code I used just from a blog related to the com interop spoken of instead, has been multiple times posted in the Internet at different locations and if I understood (language translation) it correctly they all resourced their created code from Microsoft/Windows itself.
I would offer to contribute this, but would need some help with it please:
MarshalExtension.GetActiveObject(...)
instead ofMarshal.GetActiveObject(...)
Would afterwards offer to add also a uno doc page to it in the p/invoke area including a usage sample.
What do you say? Please let me know by upvoting this cool idea!
Anyone there who wants to join an help out on this?
Beta Was this translation helpful? Give feedback.
All reactions