 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Windows Forms / Design Time / January 2007DesignerAttribute problem
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 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 > Hi all > I'm working in VB.NET. [quoted text clipped - 24 lines] > > Thank you Hi Mario, I'm becoming crazy for this problem! I think references are right: 1) designer project has a reference to controls project 2) controls project has NO references to designer project (avoiding circular references). This is the reason because I'm going to reference designers using a string instead of using GetType 3) test project (WinForms) has a reference to both controls and design projects Some other ideas please?? TIA Mario Vázquez said the following On 11/01/2007 8.18: > Hi Greco, > [quoted text clipped - 33 lines] >> >> Thank you Hi Greco, I think the wrong point is: > 2) controls project has NO references to designer project... 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 so), you just can invert points 1 and 2. If this is not the case, as far I know, the only solution is to join again your projects in one in order that all the components involved can find themselves, but well, this is not what you want, i know... :S ----- Original Message ----- From: "Greco" <submissionsSPAMFREE@SPAMFREEnaxosdev.com> Newsgroups: microsoft.public.dotnet.framework.windowsforms.designtime Sent: Thursday, January 11, 2007 10:40 AM Subject: Re: DesignerAttribute problem > Hi Mario, > I'm becoming crazy for this problem! [quoted text clipped - 48 lines] >>> >>> Thank you Hi Greco, I think the wrong point is: > 2) controls project has NO references to designer project... 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 so), you just can invert points 1 and 2. If this is not the case, as far I know, the only solution is to join again your projects in one in order that all the components involved can find themselves, but well, this is not what you want, i know... :S ----- Original Message ----- From: "Greco" <submissionsSPAMFREE@SPAMFREEnaxosdev.com> Newsgroups: microsoft.public.dotnet.framework.windowsforms.designtime Sent: Thursday, January 11, 2007 10:40 AM Subject: Re: DesignerAttribute problem > Hi Mario, > I'm becoming crazy for this problem! [quoted text clipped - 48 lines] >>> >>> Thank you Hi Mario Mario Vázquez said the following On 11/01/2007 15.07: > Hi Greco, > [quoted text clipped - 8 lines] > themselves, but well, this is not what you want, i know... > :S Yes, you are right. Maybe the only solution should be join again the two projects and start over again. Thank you for your help, it was valuable! Greco 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, > [quoted text clipped - 33 lines] >> >> Thank you
Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.