Booting the computer after a meetup with some red wine and philosophical discussions, and finding the browser tabs full of C64 code and Rider open with my Ilasm code is a sign of a night well spent.
November 28, 2025 at 10:54 AM
Booting the computer after a meetup with some red wine and philosophical discussions, and finding the browser tabs full of C64 code and Rider open with my Ilasm code is a sign of a night well spent.
Past week, 3F's assembler #ILAsm 9.4 + #DllExport 1.8.1 are rolled out with PDB support MSF/BSJB and minor improvements & fixes
I also drafted `dotnet build` support but… time to focus on other projects such as #Conari to release lighter modules due to reduced ton of delegates; +more as #opensource
I also drafted `dotnet build` support but… time to focus on other projects such as #Conari to release lighter modules due to reduced ton of delegates; +more as #opensource
![Illustrates debugging an exported function ([DllExport] attribute) for .NET 9/8/7/6 at runtime in Visual Studio 2022 for 3F's assembler 9.4 and using Conari 1.5 to access it easily](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:foxpypfkkwrhetpysf43g5mt/bafkreihihtig2aye6i4uibir6u76onbpgyv6gfzgm3lbrfmp56yvddghfq@jpeg)
June 11, 2025 at 5:40 PM
Past week, 3F's assembler #ILAsm 9.4 + #DllExport 1.8.1 are rolled out with PDB support MSF/BSJB and minor improvements & fixes
I also drafted `dotnet build` support but… time to focus on other projects such as #Conari to release lighter modules due to reduced ton of delegates; +more as #opensource
I also drafted `dotnet build` support but… time to focus on other projects such as #Conari to release lighter modules due to reduced ton of delegates; +more as #opensource
I am happy to answer any questions on how ILAsm and 6502 is similar github.com/bjartwolf/An...
I have considered writing ILAsm for 6502 developers, but I am checking out the market first.
I have considered writing ILAsm for 6502 developers, but I am checking out the market first.
github.com
June 3, 2025 at 4:22 PM
I am happy to answer any questions on how ILAsm and 6502 is similar github.com/bjartwolf/An...
I have considered writing ILAsm for 6502 developers, but I am checking out the market first.
I have considered writing ILAsm for 6502 developers, but I am checking out the market first.
I like that I can use the same trick for directions, that is using unsigned 8-bit integers (kind of the default for C64...) for wrapping directions without adding branches (there is no if-statements in ILAsm...) github.com/bjartwolf/il...
ilant/Ant.il at 05b9e0cf4912271ed0a908eb5a01e56976bd61b8 · bjartwolf/ilant
Contribute to bjartwolf/ilant development by creating an account on GitHub.
github.com
June 3, 2025 at 4:21 PM
I like that I can use the same trick for directions, that is using unsigned 8-bit integers (kind of the default for C64...) for wrapping directions without adding branches (there is no if-statements in ILAsm...) github.com/bjartwolf/il...
And then I was like, how is it to program in it... And I have written Langton's ant in C64 assembly so I thought perhaps I should "port" it too ILAsm.
June 3, 2025 at 4:19 PM
And then I was like, how is it to program in it... And I have written Langton's ant in C64 assembly so I thought perhaps I should "port" it too ILAsm.
Mostly because we (as in lambda-club people) was watching a talk at NDC on different languages, including stack languages and then we kind of discussed ILAsm being a stack language.
June 3, 2025 at 4:18 PM
Mostly because we (as in lambda-club people) was watching a talk at NDC on different languages, including stack languages and then we kind of discussed ILAsm being a stack language.
Why are you hand-writing ilasm?
June 3, 2025 at 4:16 PM
Why are you hand-writing ilasm?
Having written ILAsm for a long weekend, coming back to C# and F# does feel nice.
June 3, 2025 at 4:13 PM
Having written ILAsm for a long weekend, coming back to C# and F# does feel nice.
I could find some of the registers in my machine there, but that is about it. I think mapping what this is, is duper difficult. But my learning so far is that ILAsm is not very hard, it seems to have not changed in many years and seems to be fairly simple.
May 31, 2025 at 12:27 PM
I could find some of the registers in my machine there, but that is about it. I think mapping what this is, is duper difficult. But my learning so far is that ILAsm is not very hard, it seems to have not changed in many years and seems to be fairly simple.
I was also hoping that by writing ILAsm maybe I would be able to understand more of the machine code, but nah... I can find my numbers and adding 64 etc and some of the compares, but I am mostly lost... Like, the code isn't even 1-1 like one is used to, it just executes some optimized machine code.
May 31, 2025 at 12:19 PM
I was also hoping that by writing ILAsm maybe I would be able to understand more of the machine code, but nah... I can find my numbers and adding 64 etc and some of the compares, but I am mostly lost... Like, the code isn't even 1-1 like one is used to, it just executes some optimized machine code.
Copilot should in theory be really good at helping me with ILAsm, like there should be a lot of training data on higher level instructions to lower level code.
May 29, 2025 at 6:27 AM
Copilot should in theory be really good at helping me with ILAsm, like there should be a lot of training data on higher level instructions to lower level code.
[RuntimeAsync] ilasm/ildasm support for the MethodImpl.Async (115332) https://github.com/dotnet/runtime/pull/115332
[RuntimeAsync] ilasm/ildasm support for the MethodImpl.Async by hez2010 · Pull Request #115332 · dotnet/runtime
Implementing ilasm and ildasm support for RuntimeAsync following the spec.
Closes #115093
github.com
May 6, 2025 at 12:10 PM
[RuntimeAsync] ilasm/ildasm support for the MethodImpl.Async (115332) https://github.com/dotnet/runtime/pull/115332
[RuntimeAsync] Implement ilasm/ildasm support for the MethodImpl.Async (115093) https://github.com/dotnet/runtime/issues/115093
[RuntimeAsync] Implement ilasm/ildasm support for the MethodImpl.Async · Issue #115093 · dotnet/runtime
Re: #114675 (comment)
github.com
April 27, 2025 at 4:58 PM
[RuntimeAsync] Implement ilasm/ildasm support for the MethodImpl.Async (115093) https://github.com/dotnet/runtime/issues/115093
Build ILAsm dependencies with secure source hashing enabled in MSVC (113620) https://github.com/dotnet/runtime/pull/113620
Build ILAsm dependencies with secure source hashing enabled in MSVC by amanasifkhalid · Pull Request #113620 · dotnet/runtime
BinSkim flagged the parser ILAsm directly links in for not being built with secure source hashing enabled in MSVC (issue). Modern MSVC versions should default to using SHA-256 to compute source fil...
github.com
March 17, 2025 at 6:30 PM
Build ILAsm dependencies with secure source hashing enabled in MSVC (113620) https://github.com/dotnet/runtime/pull/113620
Reverse Engineer & Patch a .NET DLL or EXE | ILDASM & ILASM Tutorial | Hacking .NET DLLs www.reddit.com/r/ReverseEng...
Reverse Engineer & Patch a .NET DLL or EXE | ILDASM & ILASM Tutorial | Hacking .NET DLLs
www.reddit.com
March 2, 2025 at 4:13 AM
Reverse Engineer & Patch a .NET DLL or EXE | ILDASM & ILASM Tutorial | Hacking .NET DLLs www.reddit.com/r/ReverseEng...
Reverse Engineer & Patch a .NET DLL or EXE | ILDASM & ILASM Tutorial | Hacking .NET DLLs
#csharp #dotnet
#csharp #dotnet
Reverse Engineer & Patch a .NET DLL or EXE | ILDASM & ILASM Tutorial | Hacking .NET DLLs
Posted in r/csharp by u/paulpjoby • 0 points and 0 comments
old.reddit.com
February 27, 2025 at 8:43 PM
Or compile the COBOL as either bytecode or ilasm and treat the COBOL as a set of library routines via your preferred framework... or make it a REST service. You don't need to use any virtualization at all.
January 10, 2025 at 12:53 AM
Or compile the COBOL as either bytecode or ilasm and treat the COBOL as a set of library routines via your preferred framework... or make it a REST service. You don't need to use any virtualization at all.
Delete dead code in ilasm PE writer (111218) https://github.com/dotnet/runtime/pull/111218
Delete dead code in ilasm PE writer by jkotas · Pull Request #111218 · dotnet/runtime
github.com
January 8, 2025 at 10:37 PM
Delete dead code in ilasm PE writer (111218) https://github.com/dotnet/runtime/pull/111218
Fix reloc type produced by ilasm in PE64 images (111212) https://github.com/dotnet/runtime/pull/111212
Fix reloc type produced by ilasm in PE64 images by jkotas · Pull Request #111212 · dotnet/runtime
Fixes #111189
github.com
January 8, 2025 at 8:01 PM
Fix reloc type produced by ilasm in PE64 images (111212) https://github.com/dotnet/runtime/pull/111212
Invalid image produced by ilasm in .NET 9.0 (111189) https://github.com/dotnet/runtime/issues/111189
Invalid image produced by ilasm in .NET 9.0 · Issue #111189 · dotnet/runtime
Repro Create a new C# console project mkdir C:\work\ilx64 cd C:\work\ilx64 dotnet new console Build and run the created project dotnet run Move to the output folder cd .\bin\Debug\net9.0\ Verify th...
github.com
January 8, 2025 at 7:20 AM
Invalid image produced by ilasm in .NET 9.0 (111189) https://github.com/dotnet/runtime/issues/111189
1. Take an early version of Roslyn and decompile it to IL
2. Take ILASM and re-produce Roslyn
3. Then bootstrap Roslyn through successive versions to current version.
Step 2 is using an independent toolchain + IL to produce a minimal compiler
2. Take ILASM and re-produce Roslyn
3. Then bootstrap Roslyn through successive versions to current version.
Step 2 is using an independent toolchain + IL to produce a minimal compiler
December 2, 2024 at 9:31 PM
1. Take an early version of Roslyn and decompile it to IL
2. Take ILASM and re-produce Roslyn
3. Then bootstrap Roslyn through successive versions to current version.
Step 2 is using an independent toolchain + IL to produce a minimal compiler
2. Take ILASM and re-produce Roslyn
3. Then bootstrap Roslyn through successive versions to current version.
Step 2 is using an independent toolchain + IL to produce a minimal compiler
Can take any functioning compiler and convert it to IL which is .NET assembly. ILASM can then convert it to DLL / EXE that represent the root compiler. ILASM is a C++ tool and given there are bootstrapped C++ compilers it's a pure starting point for bootstrapping managed tools.
December 2, 2024 at 9:05 PM
Can take any functioning compiler and convert it to IL which is .NET assembly. ILASM can then convert it to DLL / EXE that represent the root compiler. ILASM is a C++ tool and given there are bootstrapped C++ compilers it's a pure starting point for bootstrapping managed tools.
Yeah, root toolset. The most basic tool is a very simple assembler. M2-Planet is a good starting point if you're interested.
ilasm would be possible, but I'm not sure I really get how?
In the end compiling and running some level of modern .NET requires not only compiling C#, but also running CIL?
ilasm would be possible, but I'm not sure I really get how?
In the end compiling and running some level of modern .NET requires not only compiling C#, but also running CIL?
December 2, 2024 at 7:58 PM
Yeah, root toolset. The most basic tool is a very simple assembler. M2-Planet is a good starting point if you're interested.
ilasm would be possible, but I'm not sure I really get how?
In the end compiling and running some level of modern .NET requires not only compiling C#, but also running CIL?
ilasm would be possible, but I'm not sure I really get how?
In the end compiling and running some level of modern .NET requires not only compiling C#, but also running CIL?
Ah, that kind of bootstrap. That all depends on what is a viable seed for the initial compiler? Basically, have to start with an root toolset and what is valid for that? Is ilasm a valid starting point given that it's written entirely in C++? If so then bootstrapping is quite easy ;)
December 2, 2024 at 6:46 PM
Ah, that kind of bootstrap. That all depends on what is a viable seed for the initial compiler? Basically, have to start with an root toolset and what is valid for that? Is ilasm a valid starting point given that it's written entirely in C++? If so then bootstrapping is quite easy ;)