	*Welcome to the ABC DLL Toolkit Home page*
	*Introducing the ABC DLL Toolkit*
	*Have you ever needed to have multiple data dictionaries in an app?*
	*Have you ever seen: Link Error: Group or Segclass exceeds 64K, linking a 16 bit data DLL?*
	*Have you ever wanted to compile your class library w/o hand coding the EXP file?*
	*Have you ever wanted to compile an app w/o including all the classes in your Libsrc directory?*
	*Have you ever wanted to have separate project directories for project specific ABC classes?*
	*Have you ever tried to call a DLL from another DLL w/o including it in your main EXE?*
	*Have you ever needed to load a data DLL, to be used by only one DLL in your app?*
	*Have you ever wanted to modify the shipping classes for a specific project and still maintain the standard classes for other apps?*
	*Have you ever modified the ABC classes only to lose your changes with the newest release?*

If you answered yes to any of the above questions then you’ve come to the right place!

	Toolkit Features


	The Beta release will be available for download October 8. Pricing is $99.00US for the Standard version and $149.00 for the Pro
	Please Contact Mitten Software for purchase information. Phone 1-800-825-5461 US or 612-745-4941 International
	Download Page

	*The almost complete Manual is available for download from the Download page.*

	The rest of this page is excerpted from the Manual.
	Introduction
	The ABC DLL Toolkit is a template-based solution to the above problems that does not modify either the shipping ABC classes or templates. Only the Pro version allows the use of other directories besides Libsrc, but all other features are available in the standard edition. The essential premise of the ABC DLL Toolkit is that you as the developer can decide how your apps should be linked not some guy in London. The primary assumption here is that you want to separate your Code and Data DLLs. Create one or many Files DLLs that can be linked to specific DLLs not just the main exe. Break your ABC compliant class libraries up into multiple DLLs for any number of reasons, to allow linking under 16 bit or to create demo DLLs and other easy to distribute components.

	This is a very powerful tool which “hacks” into the heart of the ABC Template/ABC Class paradigm, use it with caution. Always back up your apps before adding this extension. That being said, I have never had a corrupted app in all my testing, even tho I probably locked or GPF’d the IDE a couple hundred times getting this all to work. It started out as an exercise to see if it was possible to eliminate the “Reading ABC Classes” message that you get at least once a session when working in the IDE. After considerable study (and many lockups) I realized that without major restructuring of the ABChain.tpl, my original goal was not attainable. However, I realized that there was a way to “hack” the system, to allow all the features I have described. Actually it’s not a “hack”, more or an artful “kludge”, but that’s what template writing is all about anyway.:)

	The rest of this document is divided into “Scenarios” or chapters in which I will explain the various switches to set for different linking options. Please take the time to at least look at the pictures<g> you can see which settings are needed. Some General Words of Caution: When adding this template to existing apps, go to the project directory and delete all the existing generated files, especially all Libs and Exp files. Also when things go bad and you get either duplicate symbol or unresolved external link errors, do the same thing. And there is still one rule that we can’t break: Only one DLL shall export Globals, although in the course of template code generation I do bend it a little.

	Table of Contents
	1. The Basic Scenario – Our Files DLL is split up into a Files DLL and a Classes DLL.
	2. The Basic Scenario Plus – We can’t compile this thing 16 bit, so we break up our Classes DLL into ABCLib16 and Other16 DLLs. This also allows us to create “Generic” DLL’s for any of our classes.
	3. The Multi-Dictionary Scenario – We take two basically unrelated apps and combine them under one Application.
	4. The Advanced Multi-Dictionary Scenario – Here each DLL initializes it’s own Files DLL
	5. The DLL Chain Scenario – Let’s get all those Libs out of our main exe and put them only in the DLLs that call them.
	6. The Advanced Class Scenario – We move all our third party ABC compliant classes to a new directory. (Pro version only)
	7. The Advanced Class Scenario Redux – We call our modified OEM* ABC classes from an Alternate directory. (Pro version only)

Welcome to the ABC DLL Toolkit Home page

Introducing the ABC DLL Toolkit

Toolkit Features

Introduction

Table of Contents

1. The Basic Scenario – Our Files DLL is split up into a Files DLL and a Classes DLL.

2. The Basic Scenario Plus – We can’t compile this thing 16 bit, so we break up our Classes DLL into ABCLib16 and Other16 DLLs. This also allows us to create “Generic” DLL’s for any of our classes.

3. The Multi-Dictionary Scenario – We take two basically unrelated apps and combine them under one Application.

4. The Advanced Multi-Dictionary Scenario – Here each DLL initializes it’s own Files DLL

5. The DLL Chain Scenario – Let’s get all those Libs out of our main exe and put them only in the DLLs that call them.

6. The Advanced Class Scenario – We move all our third party ABC compliant classes to a new directory. (Pro version only)

7. The Advanced Class Scenario Redux – We call our modified OEM* ABC classes from an Alternate directory. (Pro version only)