You want to use unique names for all your libraries so references don't get confused. This wouldn't make a difference if you used the GAC or not.

>Thanks for your help I am getting closer. I was a more than dissapointed to understand that part of the subclassing process is to compile to a .dll. It looks like changes to classes in the hierarchy will be less dynamic/easy/immediate as in VFP.
>
>I can't see my way through this though...
>
>I create a global class to all of my development named aAppLib.dll.
>The assembly is created as:
>j:\Development\NET\VB.NET\LIBS\aAppLib.dll.
>NameSpace: aAppLib
>
>I subclass to customer a's development Area. CustA.aAppLib.dll This Assembly is global to all of Customer A's projects.
>The assembly is created in:
>j:\Customer Files\CustomerA\Common\Libs\CustA.aAppLib.dll
>NameSpace: CustA.aAppLib
>
>Next I subclass to customer a's first project. CustA.Project1.aAppLib.dll This assembly is global only to customer A's Project 1.
>The assembly is created in:
>j:\Customer Files\CustomerA\Project1\Libs\CustA.aAppLib.dll
>NameSpace: CustA.Project1.aAppLib
>
>If while developing in Customer A/Project 1. I use
>Imports CustA.aAppLib or I decide to go to the top of the hierarchy and use Imports aAppLib (bad example but I need to use for point)...how does the dev enviroment find all of this at compile time and even more so during Development Runtime (testing). In development does the GAC come into play here since these assemblies are outside the folder path of j:\Customer Files\CustomerA\Project1.
>
>
>
>
>
>
>
>
>
>
>
>
>>As a VFP developer, you have a leg up on VB developers learning .NET, since they have no experience with inheritance. The skills you have aquired will translate over to developing your directory and library structures in .NET. In .NET you don't have the options like you do in VFP (SCX vs. VCX vs. PRG). I have found that my directory structures and libraries work very well within .NET. I separate code into small reusable components that can be called from numerious business objects or methods. You have a organization if libraries that works well for you with VFP, do you have concerns of how a similar structure will work in .NET? In the past with VB, you had to reorganize how you laid out your project since inheritance was not in the picture. Now with .NET, there is much more similarities to VFP. The biggest difference between the two is in the case of working with data. However, your business objects and data objects can abstract the differences.