Hello All,
I have been a junior level C# developer since 2016. I programmed in qbasic and a little bit of c plus plus in high school and I will be 37 this year so I am starting assembler a little late. I had a math teacher in high school who introduced me to assembly, I think it was a 68000 cpu and called a heath kit that’s all I remember. This last week, I’ve been using Windows System Programming by Johnson M. Hart to understand windows better. I’ve also found archive.org is good for “Win32” programming, most books being 9x/NT4 and Win2000, but they seem to run fine on my killer Win10 machine with Visual Studio 2015. While learning the “Win32” api I am sticking with C mostly as I am wanting to cover the API directly and QUICKLY. I keep making mess after mess. Those messes seem like a no in coding and certainly assembly coding. Thinking about that, tonight I took a break to see if I could get OllyDbg to pick up the C source and disassembly of a very poorly written Win32 C program. It is actually the first Win32 program I have ever successfully written after a few failed attempts in MASM32. Does anyone know if Visual Studio or Hutch’s MASM32 can or will, with 32 bit assembly, produce the PDB files necessary to debug x86 assembly rather than the C shown here? Part of my original barrier to learning assembly was that I didn’t understand how to get a debugger working well and didn’t have much time to figure it out. Based on this screen shot I might have more success with OllyDbg for debugging. I guess I could use MASM32 or ml.exe with the different Visual Studio versions. I could google debugging symbols from MASM32 or something. For clarity in understanding my story, I also figured out that I could use VS for debugging in masm style assembler. I did this by telling VS that I wanted to build MASM as a build target and by changing the include and library files to point to the \masm32\include and \masm32\lib folders directly rather than (or in addition to) the typical C and C++ libraries and headers in the VS project settings. Then just add a ASM file and code. Well I hope people find this as exciting as I do. I am wanting to give up on the C#/Angular life and switch to C, Win32 and very likely masm assembler. I find been impressed with what Security Now and Steve brings for years. Also, I learned some of the win32 api by using a API monitor, I reversed sysinternals desktop.exe program and if worked, I’ve got the same multiple desktop functionality in my poorly written application. I did most of that in a XP VM and it worked, the crap code in the screen shot is where started that project with my main OS, Win10. Feel free to reply, I would be happy to make friends.
I have been a junior level C# developer since 2016. I programmed in qbasic and a little bit of c plus plus in high school and I will be 37 this year so I am starting assembler a little late. I had a math teacher in high school who introduced me to assembly, I think it was a 68000 cpu and called a heath kit that’s all I remember. This last week, I’ve been using Windows System Programming by Johnson M. Hart to understand windows better. I’ve also found archive.org is good for “Win32” programming, most books being 9x/NT4 and Win2000, but they seem to run fine on my killer Win10 machine with Visual Studio 2015. While learning the “Win32” api I am sticking with C mostly as I am wanting to cover the API directly and QUICKLY. I keep making mess after mess. Those messes seem like a no in coding and certainly assembly coding. Thinking about that, tonight I took a break to see if I could get OllyDbg to pick up the C source and disassembly of a very poorly written Win32 C program. It is actually the first Win32 program I have ever successfully written after a few failed attempts in MASM32. Does anyone know if Visual Studio or Hutch’s MASM32 can or will, with 32 bit assembly, produce the PDB files necessary to debug x86 assembly rather than the C shown here? Part of my original barrier to learning assembly was that I didn’t understand how to get a debugger working well and didn’t have much time to figure it out. Based on this screen shot I might have more success with OllyDbg for debugging. I guess I could use MASM32 or ml.exe with the different Visual Studio versions. I could google debugging symbols from MASM32 or something. For clarity in understanding my story, I also figured out that I could use VS for debugging in masm style assembler. I did this by telling VS that I wanted to build MASM as a build target and by changing the include and library files to point to the \masm32\include and \masm32\lib folders directly rather than (or in addition to) the typical C and C++ libraries and headers in the VS project settings. Then just add a ASM file and code. Well I hope people find this as exciting as I do. I am wanting to give up on the C#/Angular life and switch to C, Win32 and very likely masm assembler. I find been impressed with what Security Now and Steve brings for years. Also, I learned some of the win32 api by using a API monitor, I reversed sysinternals desktop.exe program and if worked, I’ve got the same multiple desktop functionality in my poorly written application. I did most of that in a XP VM and it worked, the crap code in the screen shot is where started that project with my main OS, Win10. Feel free to reply, I would be happy to make friends.