Re: DesignerAttribute problem

Hi all
I just tried to replace my custom designer with standard ParentControlDesigner:


DesignerAttribute("System.Windows.Forms.Design.ParentControlDesigner, System.Design")> _

but still NOT works. If the statement above is correct, I'm starting to think this is a bug...

Some ideas?

Thanks



Mario Vázquez said the following On 11/01/2007 8.18:
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


.

Relevant Pages

  • Re: DesignerAttribute problem
    ... If controls can't instantiate its designers, how they are supposed to work? ... If your designers does not need to reference your controls (i don't think ... WinForms test project. ...
    (microsoft.public.dotnet.framework.windowsforms.designtime)
  • Re: DesignerAttribute problem
    ... If controls can't instantiate its designers, how they are supposed to work? ... If your designers does not need to reference your controls (i don't think ... WinForms test project. ...
    (microsoft.public.dotnet.framework.windowsforms.designtime)
  • Re: DesignerAttribute problem
    ... controls project has NO references to designer project. ... Maybe you are not adding the reference to the designers project by using the "project references" tab. ... designers are not resolved when I test my controls in a WinForms test project. ...
    (microsoft.public.dotnet.framework.windowsforms.designtime)
  • DesignerAttribute problem
    ... I have one solution (controls and components) that contains two projects: one with the designers and another project with the controls and the components. ... Both main assembly and designers assembly are correctly copied to the Debug folder of my test project, but controls are working without a designer yet! ...
    (microsoft.public.dotnet.framework.windowsforms.designtime)
  • Re: Run/design time packages
    ... > Should I include my designers in the same assembly as my controls? ... Some of that support is in the .Design namespace, ...
    (microsoft.public.dotnet.framework.aspnet.buildingcontrols)
Loading