Re: DesignerAttribute problem
- From: "Mario Vázquez" <alguien@xxxxxxxxxxxxx>
- Date: Thu, 11 Jan 2007 08:18:23 +0100
Hi Greco,
Maybe you are not adding the reference to the designers project by using the
"project references" tab. If you don't do it this way, VS often begins to do
strange things...
Hope it helps,
Mario Vazquez
"Greco" <submissionsSPAMFREE@xxxxxxxxxxxxxxxxxxxx> escribió en el mensaje
news:OvQAo%23LNHHA.3952@xxxxxxxxxxxxxxxxxxxxxxx
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: Greco
- Re: DesignerAttribute problem
- From: Greco
- Re: DesignerAttribute problem
- References:
- DesignerAttribute problem
- From: Greco
- DesignerAttribute problem
- Prev by Date: DesignerAttribute problem
- Next by Date: Re: DesignerAttribute problem
- Previous by thread: DesignerAttribute problem
- Next by thread: Re: DesignerAttribute problem
- Index(es):
Relevant Pages
|
Loading