dasm | Macro assembler with support | Emulator library

Static fields are initialized as part of static constructor or type initializers. When using ildasm you can find the string in .cctor

https://johnnycode.com/2013/07/19/fixing-assembly-binding-redirect-errors/

I had somehow left the xmlns attribute out of my assemblyBinding element.

Just use a subquery or CTE. I can't figure out the actual logic you want, but the structure looks like this:

Aha, ASCII encoding vs. Commodore screen codes. We've all been there. You have a few options:

1. Don't write directly to screen memory, but use the Kernal CHROUT routine instead (probably via the higher-level string-output routine). Then all you have to worry about is the differences between ASCII and PETSCII, but that's a story for another bed-time. Also, this is good for text but sucks for games as the Kernal is s-l-o-w compared to direct writes.

2. Write a little conversion routine that runs when your program starts, eats your string table, and spits out converted screen code equivalents. Fast and efficient, provided your strings are all together and you're not writing a ROM-based application (which would not be able to do an in-place conversion).

3. Write a DASM pre-processor which runs before DASM in your build script and basically does the same conversion as #2 above, but to the sourcecode before the assembler sees it. This can be a bit gnarly, and you have to be sure to back-up the original source before munging it.

4. Get the DASM sourcecode and patch it to invoke a user-exit for a new data-type (for screen codes) that does the same as #2 but on-the-fly during assembly. Very gnarly.

5. Use lower-case letters in your strings, which will translate to upper-case screen code equivalents during assembly. You may have overlooked the fact that what you're seeing is the shifted representation of the characters in the string, which in the default display mode is graphics symbols.

Speaking from experience of all 5 options, I've settled on #2.

Also: switch to KickAssembler, which

• is newer, and actively maintained
• offers more powerful features
• integrates very well with VICE for debugging