Hi, thanks for viewing this.

I'm a software writer.

Some would prefer the term "firmware", which is okay.

I'm mainly involved in embedded systems, where my real smarts are in low level code; really low, like watching the pins and registers and ports and control bits and blah blah blah.

My current task is to develop a Windows C# GUI for an embedded device on which I wrote the code.

I created this account on StackOverFlow.com, hoping that I can ask a lot of questions about C#.

In the event that you have questions about assembly language in an embedded system, there is a good chance that I can give you lots of useful answers. I'm okay in that stuff, 5 or 10 years doing it for a paycheck, plus another 10 years before that in the ancient PC world; yes, there actually were computers before the internet.

Oh, and yes, assembly language is still very useful.

Negative factor here, one which must be cleared up way before we form a helping relationship: you can't be a college student looking for a professional to debug your assignments for you; or to write your code for you; or to design the architecture for you; or so on. That is the student's job, and I would be hurting you by "helping" you do that.

(And just for the record, paying money for such an activity is not "professional" in any sense of the word.)

With that said, if there is something immediately obvious which you are missing with respect to assembly language, I might be useful for a quick answer.

So, for the moment, I know a decent amount of stuff about the PIC24 (just did about 30 thousand lines of assembly language code this year) plus a half a dozen other little chips and microcontrollers; while at the same time I'm quite the eager student in matters of C# and GUIs and Serial Ports and graphs and all that stuff.