Click here to Skip to main content
15,885,767 members
Articles / Desktop Programming / Win32

Moving Memory in .NET using VB and the CIL

Rate me:
Please Sign up or sign in to vote.
4.98/5 (42 votes)
22 Jun 2014CPOL10 min read 36.2K   35  
Topics and methods on programming in .NET and performance considerations

Views

Daily Counts

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Software Developer
United States United States
I have been programming in VB/VB .NET and Windows for a very long time.

I have been programming, in general, for a very very long time.

Started in C/C++ under DOS (when I was 10, in 1986!). I even wrote a FOSSIL driver in assembly (for those of you who remember what a FOSSIL is, you're a fossil, I'm a fossil)... so I got a book that taught me serial port interrupt driven communications routines in C and ASM. Then I moved on to Pascal. Pascal disappeared and became unavailable to my youth and poorness (when it became Delphi).

Moved on to VB 6, from VB 6 I discovered the Windows API and, in fact, I am developing an ever more exhaustive port of the Windows API into VB .NET.

(I recently just reinstalled my VB 6 compiler on my Windows 8.1 system. Windows 8.1 made several protests and at least one dialog box suggested I needed therapy, I think ... but it still ran, and compiled! I use it mainly to reference my ancient projects to slowly port them into .NET ... yes, still. )

Now, here I am, years later, still learning, still working with VB (and to a lesser extent C# and to an even lesser extent C++).

I've been concentrating on getting good practice with WPF and WCF and all of the other neat Microsoft technologies of the current era.

Comments and Discussions