RunSharp is a runtime IL generator based on Reflection.Emit and IKVM which allows you to emit IL in a way similar to writing normal C# code.
It's a layer above the standard .NET Reflection.Emit API, allowing to generate/compile dynamic code at runtime very quickly and efficiently (unlike using CodeDOM and invoking the C# compiler).
* .NET Standard 2.1 (including .NET Core 3 and .NET 5)
* .NET 2.0 and higher including .NET 4 (also IKVM version available)
* Windows Phone 8
* Silverlight 5
The IKVM version has also an ability to emit NET 2.0 and .NET 4.0 assemblies (while running on, for example, .NET 3.0).
This package is a fork of TriAxis.RunSharp (the original is now abandoned).
Install-Package aqla.runsharp -Version 1.0.23
dotnet add package aqla.runsharp --version 1.0.23
<PackageReference Include="aqla.runsharp" Version="1.0.23" />
paket add aqla.runsharp --version 1.0.23
#r "nuget: aqla.runsharp, 1.0.23"
// Install aqla.runsharp as a Cake Addin #addin nuget:?package=aqla.runsharp&version=1.0.23 // Install aqla.runsharp as a Cake Tool #tool nuget:?package=aqla.runsharp&version=1.0.23
* 126.96.36.199 - added .NET standard 2.1 support and .NET 5 tests, removed separate Xamarin.Android (use .NET Standard build instead)
* 188.8.131.52 - fix for explicit interface implementation, added Android platform
* 184.108.40.206 - IKVM reference won't be added for nuget installations
* 220.127.116.11 - multidimensional array access, fix for AND/OR operands
* 18.104.22.168 - added nullables support, multiple improvements
* 0.2.0.5 - operand leaking detection
* 0.2.0.4 - added support for Silverlight 4
* 0.2.0.3 - added support for Windows Phone 8
* 0.2.0.0 - initial fork release:
- added IKVM support
- examples converted to tests
- added peverify checks
- fixed multiple bugs
- No dependencies.
- No dependencies.
- Lokad.ILPack (>= 0.1.6)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on aqla.runsharp:
AqlaSerializer is intended to serialize objects, not just data. What the difference? Data serializers don't care much about language runtime specifics like references, inheritance, etc. In contrast, an object serializer should take such things into account. AqlaSerializer primary goal is to support important .NET features like nested collections, multi-dimensional arrays, references, etc. And it still supports Google Protocol Buffers format. Like protobuf-net AqlaSerializer makes possible to store objects as a small in size binary data (far smaller than xml). And it's more CPU effective than BinaryFormatter and other core .NET serializers (which could be unavailable on your target platform). Its format is designed to be: small in size - efficient data storage (far smaller than xml) cheap to process - both at the client and server platform independent - portable between different programming architectures extensible - to add new data to old messages. The implementation is compatible with most of the .NET family, including .NET 2.0/3.0/3.5/4.0, .NET Standard 2.1 (.NET Core 3, .NET 5), Windows Phone 8, Silverlight, Xamarin.Android, etc. The code is heavily based on Marc Gravell's protobuf-net but there are a lot of improvements and fixes. The original protobuf-net project contains many "red" unit tests but I managed to fix a lot of them. Some build configurations may be not available through nuget, you can download their binaries manually from github (use Project Site link).
This package is not used by any popular GitHub repositories.