Repository navigation
Support netstandard2.0 in ILRepack.Lib nuget package #409
Description
This is more of a question of "why it's not done yet?":
- Mono.Cecil and other dependencies do support netstandard2.0
- There's the .NET 8 tool in the repo which is actually using dependency libs in the netstandard2.0 configuration so it's working and tested
- Codebase is explicitly .NET 9 friendly overall, e.g. removing the BinaryFormatter (the reason I had to revive my involvement in the ilrepack, to be honest, is the BinaryFormatter breaking things)
- .NET environment overall is moving away from netframework, so many (and, with time, most?) of the library consumers will be netstandard and not netframework
- Speaking of specific examples is "dotnet msbuild" which is explicitly not netframework
So, the proposal would be:
- Create a new ILRepack.Lib project in a new folder, using ILRepackTool as a template
- Dual-target net472 and netstandard2.0
- Publish a nuget package out of it
Reacted by Ichiro Sugimoto
Activity
KirillOsenkov commentedon Jun 11, 2025
I don't see why we couldn't, it's probably only because no one cared about it so far
lextm commentedon Jun 11, 2025
I agree with @KirillOsenkov that this is doable but who really cares? .NET 8/9/10 projects can consume net472 NuGet packages freely.
Alexx999 commentedon Jun 11, 2025
Well, you can consume net472 DLL
But it's an API minefield - might work, might not work, all depending on what exact execution path you end up depending on inputs and params.
For example, Cecil has plenty of ifdefs for netstandard/netcore - I imagine that's due to some APIs not being present, other dependencies might have that too.
lextm commentedon Jun 11, 2025
@Alexx999 if you follow that repo (I follow it because Obfuscar depends on Mono Cecil too), you should know there are potential much more (but in general, you can do just little about it as downstream but to adapt).
I rather wait till real world issue reports indicate the necessity than purely something conceptual.