Yep when you have enums inside your usercontrol it freaks out and say that the enum doesn't belong to the system.componentmodel.icontainer while it doesn't really need to be. Since components is a namespace that already exists it doesn't seem to want to know the other one. But just for the enums all the rest just works fine.
Christiaan Baes
Belgium
If you want to get an answer read this FAQ faq796-2540 There's no such thing as a winnable war - Sting
Does this happen when the project name is "Components"? or when the default namespace is "Components"? By default the default namespace = the project name. If it's the namespace that is the problem, then you could still have your project named Components, but you'd have to change the namespace.
Here, everything we do is in the GFC (company name) namespace.
GFC.General
GFC.General.Functions
GFC.General.Forms
GFC.General.Controls
GFC.Data
GFC.Data.[DatabaseName]
GFC.Engines
GFC.WindowsApps.[AppName]
etc. It helps keep all of our stuff out of the frame work library's namespaces.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.