|By: Paul S. Cilwa||Viewed: 10/18/2021
||Topics/Keywords: #Freeware #VisualBasic6.0 #VisualC++||Page Views: 182|
|Here are some fun programming projects you may find useful. —You're welcome!|
It's an ill wind that blows no good. Hopefully, my winds blow benefits to all. Below find listed programming projects (and programming-related projects) I offer to any and all who can benefit.
Easily Register DLLs and OCXs
|By: Paul S. Cilwa||Topics: #ProgrammingforMicrosoftWindows||Page Views: 169|
|How to create a simple Registry merge file that will add double-click registration (and context menu unregistration) to DLLs and OCXs on your computer.|
Anyone who's had to wrestle with the hundreds and hundreds of Dynamic Link Libraries (DLLs) and tool libraries (OCXs) in a typical Windows system can certainly appreciate the sentiment. And while users don't typically have to worry about them anymore, developers still must give a care as to making sure the correct libraries are present; the correct versions of libraries are present; and sometimes, must even jump back and forth between versions to determine the source of a bug or to compare features to an older version of a client program.
|By: Paul S. Cilwa||Topics: #ProgrammingforMicrosoftWindows||Page Views: 0|
|How to extend VB.NET's String class to make it even more powerful.|
Visual Basic, and before that BASIC, were not originally desgined to be object-oriented languages. It's taken decades of evolution and revolution to arrive at the VB.NET we use today. But there are still quirks remaining from the old days. For example, the legacy Visual Basic (and VBA) functions such as Left() and Right() (for returning substrings) still exist in VB.NET in the Strings module, when they really should be methods of the String class itself. But not to worry, as it's easy for us to add those as extensions to the String class. Let's see how.
Visual Basic Legacy Runtime Libraries
|By: Paul S. Cilwa||Topics: #ProgrammingForMicrosoftWindows #RuntimeFiles #VisualBasic||Page Views: 162|
|Free (and ad-free!) access to Microsoft's runtime libraries for legacy versions of Visual Basic, from 1.0 through 6.0 SP6.|
Visual Basic has always produced program files (also called "executables" or "applications" but never stand-alone program files: They all, also, required a Visual Basic "runtime" library that actually contained virtually all of the Visual Basic program functions used by the programmer to make his or her program work. The original idea is that the runtime library would be a part of Windows, distributed with it and therefore not part of the overhead of disseminating a program itself. Alas, this never became the case.