Ron,

>I can see how to visually subclass a form. How do I subclass controls (I am thinking along the lines of how you do this in VFP)
>

See thread #695724 for how to subclass controls. Visual Studio .NET doesn not support visual inheritance so it must be done in code. The steps are very different then in VFP but doable.

>I am trying to understand namespace assignments in regards to the above structure.
>

Namespaces emphasize the logical structure of the application, and avoid name clashes between types with the same name in different namespaces. As far as how you want to organize your namespaces, this is really what you feel comfortable with. You can organize them similar to your directory structure or by type of objects. Namespaces don't have to be included in the same file. There can also be numerious namespaces in the same file.

>I am having a hard time understanding assemblies in relation to this. I might understand assemblies. I might only feel like I don't because I am afraid of what I don't know.
>

In the simplest case, an assembly is a single module (which is an .EXE file or a .DLL file). When you create a new project in Visual Studio .NET, that project is a single assembly. However, you can write an application the spreads classes accross different assemblies (projects) for deployment purposes.

>I am having a hard time with assembly trust since this is all located on an untrusted location to my .NET local install. I can't seem to increase the trust.

I recommend the following link that has information that is very useful for setting up security rights. Just scroll down till you see the information about setting up security.

http://www.andymcm.com/dotnetfaq.htm


I would highly recommend a book by Wrox called Visual Basic .NET Class Design Handbook - Coding Effective Classes. Even if you are a C# programmer, the information contained in the book about how to organize your classes, namespaces, and assemblies is very useful.



>I am an independent developer. I do work for several companies and have for years in VFP/Fox. My directory/file layout mirrors my framework. That structure basically states this.
>
>* All of this is layed out on one of my servers. Not local.
>
>Base - j:\Development\VFP\Classes
> \Progs
> \...
> \...
>
> DevCustomer - J:\Customer Files\Customer A
> \Customer B
> \Customer C
>
> Projects - J:\Customer Files\Customer A\Project A
> \Project B
> J:\Customer Files\Customer B\Project A
> \Project B
> ...
>
>Base.
>All of the VFP base classes are subclassed into my base classes and stored in the Base area. All other global type dev things progs, libraries etc are stored at this level as well.
>
>DevCustomer.
>When I add on a new customer. I subclass all of the base classes into that Customers directory structure. I place all specific project dependicies in the DevCustomer area.
>
>Projects. Below a customer is a folder for each project for that customer. I may or may not subclass again for a project. If so that is stored in the Customers specific project area. A customers app is never based upon base clasess. At the very least they are based upon the customer classes and maybe upon another level of subclassing specific to the project.
>
>====================
>I am attempting to duplicate this with .net.
>
>Issues.
>
>I can see how to visually subclass a form. How do I subclass controls (I am thinking along the lines of how you do this in VFP)
>
>I am trying to understand namespace assignments in regards to the above structure.
>
>I am having a hard time understanding assemblies in relation to this. I might understand assemblies. I might only feel like I don't because I am afraid of what I don't know.
>
>I am having a hard time with assembly trust since this is all located on an untrusted location to my .NET local install. I can't seem to increase the trust.