Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking. Commented Jul 22, 2024 at 12:41
  • UWP plays in a sandbox; I can't see why a UWP class library (which I use) wouldn't either. I use ".NET Standard" libraries to share code between Console, WPF and UWP; which wouldn't include UI elements. Commented Jul 23, 2024 at 20:54
  • So, the reason why I was getting the EEFileLoadException was that I did not properly export the class library as the dll was on debug mode. Fixed that issue, but now I'm getting an HRException, not sure what that means and I'm currently in the middle of figuring it out, but if you've faced the same issue by any chance, please point me in the right direction. Also, @GerrySchmitz, have you made a 'self contained deployment' for the uwp library? I don't want the user to have to install .netcore on their system, and I want all the necessary .netcore dlls packaged with my output executable. Commented Jul 24, 2024 at 6:26
  • My apps are deployed via MS Store; and I have no issue bundling UWP exe, UWP dll, and Standard dll. (I can't picture a case where I only give someone a "library") BTW, you can call into an EXE just as you can call into a dll; but all still have to be compatible. I can also deply my apps to my own remote devices via VS. The Windows Certification tests tell you when you're good to go. I hear "foreign" (i.e. "3rd party") dll's are an issue when it comes to certification. Commented Jul 24, 2024 at 17:03