What's the difference between the com and exe extensions? (2008)
Good stuff.  Good to know.  Thanks, I needed that.  Always wondered.  Good explanation, 20 years late for me to read this, but better late than never.<p>Yes, it sounds like a COM file, with no <i>relocation dictionary,</i> etc., would have to be loaded at the same virtual memory address.  IIRC one of the OP comments mentioned this.<p>Uh, more of the same, piled higher and deeper?<p>Okay, for my startup I decided to use the .NET Framework 4 with Visual Basic .NET and the usual acronyms SQL (structured query language) Server, ADO.NET (active data objects for using SQL Server), ASP.NET (active server pages for writing Web pages), IIS (Internet information server, which actually makes the TCP&#x2F;IP calls for moving the data on the Internet and runs my VB.NET program that writes the Web pages),  etc.  Okay.<p>But eventually it dawned on me that there is a lot of code running on my Windows machine that very likely is not from Visual Basic and .NET; I&#x27;m concluding that there is an older, say, Windows 95, 98, NT <i>development environment</i> based on C++ and a lot of library calls, a message queue for inputs, some entry variables and <i>call backs</i> to them, and quite a lot of functionality not also in .NET.<p>E.g., when my HP laser printer quit and  I got a Brother laser printer, my old HP&#x2F;GL (Hewlett Packard graphics language, a cute, simple thing for printing and drawing on pages) program to print files didn&#x27;t work -- the Brother printer didn&#x27;t do with HP&#x2F;GL just what my HP printer did.<p>So, via .NET I wrote a replacement for such simple printing.  Well, for writing the characters to the page, object, image, whatever it was (I don&#x27;t recall the details just now), all I could see to use was some GDI+ (graphical data interface or some such?) calls, but those seem not to be the usual way old Windows programs write to paper, graphics files, or the screen and instead there&#x27;s something else, maybe back before .NET, and I don&#x27;t know what that older stuff was.  E.g., the GDI or whatever it is didn&#x27;t let me actually calculate accurately how many pixels horizontally a string of printable characters would occupy when printed and, thus, all my careful arithmetic about alignment became just crude approximations -- no doubt Firefox, Chrome, Windows Image and FAX Viewer, etc. all use something better, more accurate.<p>So, what am I missing?  Am I supposed to get out some 20 year old books by Petzold or some such, get a Windows <i>Software Development Kit</i> or some such, review C and C++, get lots of include files organized, etc., start with some sample code that illustrates all the <i>Windows standard</i> things of a standard <i>Windows app</i> or some such?<p>Okay, but it appears that .NET does not yet replace all that old stuff?
I mean, is it possible to write a <i>full function Windows app</i> with just .NET, VB.NET&#x2F;C#?<p>Q 1.  What really is that old stuff?   Where is it?  Are there good tutorials?  E.g., if we are to explain COM files, then let&#x27;s also point to explanations of some of the other old stuff also still important?<p>Q 2. Is the functionality of that old stuff, for user level programs, maybe not for device drivers, by now all available via .NET but I&#x27;ve just not found it all yet?  If so, where is it in .NET, say, for graphics and printing the .NET <i>presentation</i> thingy or whatever?<p>The code for my startup looks fine, all seems to work, does all I intended, but still I wonder about that old stuff.  E.g., eventually I noticed that my favorite editor KEdit, apparently like
any well behaved old standard Windows program, will let me print a file.  And the printing works great!  I get a standard Windows popup window that lets me select font, font size, bold or italic, etc., and it works fine with the Brother printer.  KEdit knows some things about writing to a printer I didn&#x27;t see in .NET.  So, with just .NET, I&#x27;m missing a lot of Windows functionality?