DesignerAttribute problem
- From: Greco <submissionsSPAMFREE@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 10 Jan 2007 15:00:21 +0100
Hi all
I'm working in VB.NET.
I have one solution (controls and components) that contains two projects: one with the designers (all inherited from ControlDesigner) and another project with the controls and the components.
Before splitting mu project into two different projects, I was working on a single assembly (project) containing both designers and controls, amd Designer was specified this way:
DesignerAttribute(GetType(MyControlDesigner))
After moving my designers to a new project, I specified control's designers attribute this way:
DesignerAttribute("MyNamespace.Designers.MyControlDesigner, MyDesignerAssembly.Design, Culture=neutral")
Unfortunately, designers are not resolved when I test my controls in a WinForms test project. Both main assembly (controls) and designers assembly are correctly copied to the Debug folder of my test project, but controls are working without a designer yet!
In other words: how literal (string) references are resolved for DesignerAttribute?
Same problem with TypeConverters and TypeEditors...
What I'm missing?
Thank you
.
- Follow-Ups:
- Re: DesignerAttribute problem
- From: Mario Vázquez
- Re: DesignerAttribute problem
- Prev by Date: InstanceDescriptor problem rendering Nullable<double> constructor parameters
- Next by Date: Re: DesignerAttribute problem
- Previous by thread: InstanceDescriptor problem rendering Nullable<double> constructor parameters
- Next by thread: Re: DesignerAttribute problem
- Index(es):
Relevant Pages
|