cil
Here are 49 public repositories matching this topic...
A good example is ConfuserEx's anti tamper.
Just loading and saving the file with dnlib will remove the extra section injected by ConfuserEx and the assembly cannot be run or deobfuscated any further.
While reading the code to understand how to use this (or related) library, I found following comment in MonoMod.RuntimeDetour/NativeDetour.cs:
https://github.com/MonoMod/MonoMod/blob/86f3be60825da9328130a639a9a47ba13e49486e/MonoMod.RuntimeDetour/NativeDetour.cs#L18
I didn't find the DetourManager and I think this was meant to be DetourHelper. If so, correcting this would make everything
Are there any plans to implement the reflection system in the project, if so, do you have any idea how it will work to generate methods and classes at runtime, and execute this code?
For exemple, if we have this code:
static void Main(string[] args)
{
const string AssemblyName = "HelloWorld.dll";
var assembly = AssemblyBuilder.DefineDynamicAssembly(
-
Updated
Jun 12, 2020 - C#
-
Updated
Dec 3, 2018 - C#
-
Updated
Nov 1, 2019 - F#
-
Updated
Apr 26, 2018 - C#
-
Updated
Mar 17, 2020 - C#
-
Updated
Jan 2, 2019 - Lua
-
Updated
May 25, 2020 - C#
-
Updated
Feb 7, 2020 - C#
Many public APIs don't provide any in-editor tooltips. It would be wise to fix them to provide usage context to mod/GSL developers.
When outputting signature of entry point method as CIL assembler code, it should be marked with .entrypoint directive.
Example code:
using System;
using System.Reflection;
using CilBytecodeParser;
class Program
{
public static void Main(string[] args)
{
Console.WriteLine(CilAnalysis.MethodToText(MethodBase.GetCurrentMethod()));
Console.ReadKey();
-
Updated
Jun 8, 2020 - F#
-
Updated
Feb 6, 2020 - Python
Improve this page
Add a description, image, and links to the cil topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the cil topic, visit your repo's landing page and select "manage topics."


Originating bug report on the .net core API docs:
dotnet/dotnet-api-docs#2854
To summarize, we start with this method signature:
Compiler output is