compiling a bunch of .cls files. 1

[HerbAndEdnaWeinstein]

Hello, I've downloaded a VB developer sample for a piece of software I use (Incidentally, the software is ArcView GIS). A few things come in the download pack:

1) A group of .cls and .frm files. I'm assuming this is the source code.

2) A batch file that invokes regsrv32.exe. I'm assuming this is what registers the DLLs.

3) Two .dll files. I'm assuming this is the compiled version of the .cls. and .frm files.

I don't have a VB compiler on my machine, so I'm assuming that the source code is not being compiled into the DLLs before they are installed; the source code is just included for posterity.

**********************************************************

In one of the enclosed .cls files, I've changed a few lines of code to meet my needs. Now I want to compile the altered .cls files into a DLL.

My (possibly simple) question is this: is this simply a process of obtaining a VB compiler (I know there are free ones available), finding out which .cls and .frm files feed into which .dll, compiling them, and then running the batch file which takes care of registering the DLLs?

Thanks in advance for answering this fundamental question, I've sort of gotten into the world of code modification out of unexpected necessity

Herb Weinstein

 

[Hexonx]

It sounds like the source code is for a Visual Basic DLL project. Yes, you will need a VB compiler. I've not heard of a free VB compiler that can produce COM DLLs, which is the reason for the batch file call to regsvr32.exe.

 

[HerbAndEdnaWeinstein]

Hexonx:

THanks for replying.

After trying a few of the free compilers out there, I realized you're right that none of them that will generate a DLL.

There is a free .Net "compiler" that Microsoft has. If it produces DLLs, will I have to modify my code to conform to .Net standards, or is it backward compatible?

Thx Again,
Herb Weinstein

 

[Hexonx]

Microsoft's .NET platform no longer inherently uses COM, though it can still communicate with COM components via a shim layer called COM Interop(-erability). Compiling a .NET assembly such that is employs this layer is not a trivial task. Furthermore, your DLL will now require the .NET platform to be installed on any box that uses the DLL. From your description of the issue, the .NET path only complicates the issue.

If you are developing on the VB6 platform, I'd recommend sticking with that platform. I found VB6 Professional on the web at the following address:

http://bizrate.com/marketplace/sear...sual Basic Professional Edition ver 6 0 .html

You may even consider hiring a local contractor or consulting company to do this work for you.

HTH