Support .NET Standard 1.1
See original GitHub issueI think you can support the netstandard1.1
framework profile by just adding this target framework to the InlineIL project, a one-line change. I only needed to drop support to 1.4, but just happened to try 1.1 too.
This opens up usage of the project under some some reduced functionality (sandboxed) environments.
I made a copy of that (sans t4) in my repo and linked against it. Fody appears to be able to process it properly.
This would also inadvertently, indirectly support .NET 4.5 and other downlevel platforms.
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
NET Standard
.NET Standard is a formal specification of .NET APIs that are available on multiple .NET implementations. The motivation behind .NET Standard ...
Read more >What is .Net Standard? How it is different from .Net Core ...
The .NetStandard is versioned similar to framework versioning. The current version of .Net Standard is 1.6 and .Net Core 1.0, 1.1 supports .Net...
Read more >Understanding the .NET ecosystem: The introduction of . ...
NET Standard is the ability to target new platforms without having to recompile any of your libraries or wait for dependent library authors...
Read more >.NET Core vs .NET Framework vs .NET Standard: A Guided ...
A guide for understanding the differences between .NET, .NET Core, .NET Framework, .NET Standard, etc. by exploring the history of the platform.
Read more >What is .NET Standard and When to Use It?
NET Standard defines a set of APIs. All .NET implementations conforming to this version must support all of these APIs. The table below...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
BTW apparently
<PackageReference Update="NETStandard.Library" PrivateAssets="all" />
is the way to remove the reference.I released v1.3.6, it should be available on NuGet after validation and indexing.