stancrm is totally right. With Reflection you can call private members and that is probably what the .NEt runtime does. Visibility modifiers are mostly relevant for the compiler. With Reflection you can access everything no matter what visibility it has. This not only includes calling methods, but also accessing and changing fields which are hidden privately within external classes.

Nope. Swedish. :) --- b { font-weight: normal; }

follow the steps.. 1) Close VS.net 2) Delete the and obj folder inside of the project u trying to build. 3) now build the application. There are chances that the pdb might be the problem,:) Mind think with Ideas,not Data. No amount of Information or Data could be compared with an inspired thought. -- modified at 9:15 Tuesday 28th March, 2006

Hi You are building a Class Library (dll) look for the namespace of The class MeltPracDataGmix and add this refrence in your project using TheNamespaceThatHoldstheClassMeltPracDataGmix; C# use the namespace technique instead of the header technique C, C++ ---> #include .Net ( including C# ) ---> using System; Ahmad Shaban

What my work-around was was to create a new project (within the same solution) for containing the controls. So you'd have e.g. Application.csproj contained in Project.sln, if you create a Controls project in your solution to contain the controls. Then when you want to put them on the form VS2003 should have automatically added a toolbox entry for the control. If not you can add it to the toolbox manually. (Sometimes if an you've updated the custom control you may need to remove the assembly which contains the control from the debug/release folder of your project to force VS to get a new copy) Ed

There may be no best solution for it but here's some of my thoughts: 1. Seperate the logic and interface. You duplicate codes on the form but keeping the logics in 1 place. Probably this is too late for you to do now. 2. Have only 1 form, but a lot of switches to turn on/off the controls. But it will get very messy and confusing. I have seen forms and panels overlapping each other in one of our product and it's a nightmare just to look at the codes. 3. Put the core stuffs in a base form and inherit the forms into 2 forms (possible?), add new requirement on each new forms as required. If you have a 3rd requirement for new customer, it can support it well enough. 4. Duplicate everything into 2 forms. Harder to maintain but not as bad as (2). Out of these few, I think 1 and 3 are the better one.