Added .NET Framework interoperability to the core and started a c# binding library #1
Conversation
|
Thanks for your PR! We are not ignoring you, it's just that there isn't really much development going on with LS right now... My main question is if this couldn't be done as a module instead? Does it really require changes to the core? |
|
Adding .NET to the core seems natural to enable .NET created modules to work with Litestep just as if they were created native modules. So for an example, a configuration like:
Look and feel the same just that one lets Litestep know it should host the module in the .NET runtime. The other reason for integrating this functionality into the core is because I'm experimenting with a shell replacement for a kiosk experience. Litestep has all the basic functionality I need and the climate here is .NET (none wants to fiddle with C++) so I'm needing to accommodate developers with .NET skill sets. I wanted to contribute this functionality back to the community if its deemed useful :) |
…as adding the LsapiSharp assemblies to the sdk folder
* Started work on integrating dotnet core * Able to load .NET Core runtime inside of Litestep * Refactored CLRModule abit
|
shame .net is not open source compilable tho |
No description provided.