M
Michael Lang
Hi all...
Well I've posted this in
microsoft.public.dotnet.framework.aspnet.buildingcontrols and
microsoft.public.dotnet.framework.aspnet without a single response. I'll
try here...
I have a class deriving from System.ComponentModel.Component.
In VS 2003 I could drag it on to a web form. However I'm finding in VS 2005
whilst it functions perfectly at runtime. At design time in VS.NET 2005 you
can not drag the component on to a web form. When I select customize
toolbox and select my dll containing the component I can see the component
listed and checked. After clicking OK the component is not actually
available in the toolbox. Selecting show all, displays the component
however it is disabled (greyed out) and cannot be dragged on to a web form.
This same component works in VS.NET 2005 as it did in 2003 for Winforms
projects, but not Webforms.
It seems VS.NET 2005 has decided that my component is not applicable to
ASP.NET.
I've attempted adding the System.Web.UI.ToolboxData attribute however it
made no difference.
Can anyone explain how VS.NET 2005 decides what is and what isn't an ASP.NET
component?
If you're wondering what this component does, it's a middle tier server side
component. So it does not render HTML, however it is used by ASP.NET
controls that do render html.
If you want code to replicate it...
Just create an empty class derived from component.
Compile it add the dll to the toolbox.
Any sort of feedback would be appreciated. I've only got one dev machine at
the moment so I don't know if this is just an anomaly on my machine or not.
My feeling is though, this is by design and that I need to implement an
additional interface or add an attribute to get it to work with VS.NET 2005
ASP.NET at design time.
Michael
Well I've posted this in
microsoft.public.dotnet.framework.aspnet.buildingcontrols and
microsoft.public.dotnet.framework.aspnet without a single response. I'll
try here...
I have a class deriving from System.ComponentModel.Component.
In VS 2003 I could drag it on to a web form. However I'm finding in VS 2005
whilst it functions perfectly at runtime. At design time in VS.NET 2005 you
can not drag the component on to a web form. When I select customize
toolbox and select my dll containing the component I can see the component
listed and checked. After clicking OK the component is not actually
available in the toolbox. Selecting show all, displays the component
however it is disabled (greyed out) and cannot be dragged on to a web form.
This same component works in VS.NET 2005 as it did in 2003 for Winforms
projects, but not Webforms.
It seems VS.NET 2005 has decided that my component is not applicable to
ASP.NET.
I've attempted adding the System.Web.UI.ToolboxData attribute however it
made no difference.
Can anyone explain how VS.NET 2005 decides what is and what isn't an ASP.NET
component?
If you're wondering what this component does, it's a middle tier server side
component. So it does not render HTML, however it is used by ASP.NET
controls that do render html.
If you want code to replicate it...
Just create an empty class derived from component.
Compile it add the dll to the toolbox.
Any sort of feedback would be appreciated. I've only got one dev machine at
the moment so I don't know if this is just an anomaly on my machine or not.
My feeling is though, this is by design and that I need to implement an
additional interface or add an attribute to get it to work with VS.NET 2005
ASP.NET at design time.
Michael