Skip to content

Added .NET Framework interoperability to the core and started a c# binding library - #1

Open
Donelle wants to merge 17 commits into
lsdev:masterfrom
Donelle:master
Open

Donelle wants to merge 17 commits into
lsdev:masterfrom
Donelle:master

Conversation

@Donelle

@Donelle Donelle commented Jan 2, 2017

Copy link
Copy Markdown

No description provided.

@Tobbe

Tobbe commented Jan 10, 2017

Copy link
Copy Markdown
Contributor

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?

@Donelle

Donelle commented Jan 10, 2017

Copy link
Copy Markdown
Author

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:

LoadModule $ModuleDir$MyCSharpMod.dll clr
LoadModule $ModuleDir$MyNative.dll

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 :)

@Kreijstal

Copy link
Copy Markdown

shame .net is not open source compilable tho

* Update build docs for VS2017 and the .NET projects

Replace build_vc11.txt (VS2012, nonexistent litestep_vc11.sln) with
build_vs2017.txt covering the v141_xp toolset, the .NET Framework 3.5 SP1 /
4.6.1 / .NET Core requirements, output folders, and the sdk examples.
Describe the LsapiSharp projects in build.txt and mark the MinGW build as
out of date.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Fix the Release|Win32 build of litestep.exe

Release|Win32 inherited /MP from litestep.props, and #import (used by
CLRModule.h for mscorlib) is not supported with /MP (error C2813). It also
did not link oleaut32.lib, mscoree.lib and comsuppw.lib, which the CLR
loader needs (11 unresolved externals). Match the other three configs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Document building with VS 2022 plus the v141 tools

Verified: all four native configurations build with VS 2022 after adding
the v141 build tools and v141 Windows XP support components.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@Tobbe

Tobbe commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

@Donelle Are you still running LiteStep 🤯 Are you using it for that kiosk experience you were talking about?

@AnrDaemon

Copy link
Copy Markdown

IDK about him, but I do. It doesn't work for kiosk mode, but quite efficient as a DE, as always.
Just with a caveat about Metro apps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants