B
Beemer Biker
I have some demo code that came with a 3rd party product. This is what it
looks like (I remove html braces in case it does not print right)
Register TagPrefix="pin" Namespace="Pintexx.Components.Web.pinTab"
Assembly="pinTab"
That line of code was the 2nd line just below the Page Language="C#" ... in
default.aspx
I created a new, blank page, and attempted to copy and paste the control
onto the new page. Got an error message that the control was not registered
as follows: "This control cannot be displayed because its TagPrefix is not
registered in this Web Form."
OK, I assume I can easily fix that by copying that registration line to the
new page.
Was wondering why I got to do this in the first place? I noticed that my
web.config file has some assemblies such as:
<assemblies>
<add assembly="System.Windows.Forms, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=xxx"/>
<add assembly="System.Security, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=xxx"/>
<add assembly="Accessibility, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=xxx"/>
<add assembly="System.Runtime.Serialization.Formatters.Soap,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=xxx"/>
<add assembly="System.Deployment, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=xxx"/>
</assemblies>
Can I put that pintab registration into web.config and avoid using that
registration code snippet altogether?
So what is the difference between an Assmbly in the aspx page and an
assembly in web.config?
The 3rd party control did not come with an install and it is not in the
toolbox for VS2005.
--
======================================================================
Joseph "Beemer Biker" Stateson
http://TipsForTheComputingImpaired.com
http://ResearchRiders.org Ask about my 99'R1100RT
======================================================================
looks like (I remove html braces in case it does not print right)
Register TagPrefix="pin" Namespace="Pintexx.Components.Web.pinTab"
Assembly="pinTab"
That line of code was the 2nd line just below the Page Language="C#" ... in
default.aspx
I created a new, blank page, and attempted to copy and paste the control
onto the new page. Got an error message that the control was not registered
as follows: "This control cannot be displayed because its TagPrefix is not
registered in this Web Form."
OK, I assume I can easily fix that by copying that registration line to the
new page.
Was wondering why I got to do this in the first place? I noticed that my
web.config file has some assemblies such as:
<assemblies>
<add assembly="System.Windows.Forms, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=xxx"/>
<add assembly="System.Security, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=xxx"/>
<add assembly="Accessibility, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=xxx"/>
<add assembly="System.Runtime.Serialization.Formatters.Soap,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=xxx"/>
<add assembly="System.Deployment, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=xxx"/>
</assemblies>
Can I put that pintab registration into web.config and avoid using that
registration code snippet altogether?
So what is the difference between an Assmbly in the aspx page and an
assembly in web.config?
The 3rd party control did not come with an install and it is not in the
toolbox for VS2005.
--
======================================================================
Joseph "Beemer Biker" Stateson
http://TipsForTheComputingImpaired.com
http://ResearchRiders.org Ask about my 99'R1100RT
======================================================================