|
|
You're in the
dotnet windows forms designtime
group:DesignerAttribute problem
dotnet windows forms designtime:
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?
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@SPAMFREEnaxosdev.com> escribió en el mensaje news:OvQAo%23LNHHA.3952@TK2MSFTNGP02.phx.gbl... [quoted text, click to view] > 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 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: [quoted text, click to view] > 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@SPAMFREEnaxosdev.com> escribió en el mensaje > news:OvQAo%23LNHHA.3952@TK2MSFTNGP02.phx.gbl... >> 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 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: [quoted text, click to view] > 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@SPAMFREEnaxosdev.com> escribió en el mensaje > news:OvQAo%23LNHHA.3952@TK2MSFTNGP02.phx.gbl... >> 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,
I think the wrong point is: [quoted text, click to view] > 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 [quoted text, click to view] > 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, >> >> 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@SPAMFREEnaxosdev.com> escribió en el mensaje >> news:OvQAo%23LNHHA.3952@TK2MSFTNGP02.phx.gbl... >>> 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,
I think the wrong point is: [quoted text, click to view] > 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 [quoted text, click to view] > 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, >> >> 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@SPAMFREEnaxosdev.com> escribió en el mensaje >> news:OvQAo%23LNHHA.3952@TK2MSFTNGP02.phx.gbl... >>> 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 Mario
Mario Vázquez said the following On 11/01/2007 15.07: [quoted text, click to view] > 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 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!
Don't see what you're looking for? Try a search.
|
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
February 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |