S
Seen The Bean
Situation
Like many organizations, we're making extensive use of Custom Server
controls and have developed a set of controls that are to be used in
virtually every application that we develop. We want to be able to use those
controls in the markup of our pages without adding a <% Register %> tag just
as the controls in the "asp:" namespace are available. It would be
acceptable to setup these controls, say, once per machine (perhaps in
machine.config?), or at least per application, but no more often than that.
We've specified the assembly: TagPrefix attribute already assuming that that
was prerequisite.
Questions
1) By what mechanism does the ASP.NET parser know about these "builtin" tags
and how can we add to the list?
2) Can we cause the Visual Studio IDE to recognize these custom controls as
well so as to enable intellisense? If so, how?
I believe a great many people are interested in this capability both within
and outside of my organization. Please help!
~Cheers & Thanks
Like many organizations, we're making extensive use of Custom Server
controls and have developed a set of controls that are to be used in
virtually every application that we develop. We want to be able to use those
controls in the markup of our pages without adding a <% Register %> tag just
as the controls in the "asp:" namespace are available. It would be
acceptable to setup these controls, say, once per machine (perhaps in
machine.config?), or at least per application, but no more often than that.
We've specified the assembly: TagPrefix attribute already assuming that that
was prerequisite.
Questions
1) By what mechanism does the ASP.NET parser know about these "builtin" tags
and how can we add to the list?
2) Can we cause the Visual Studio IDE to recognize these custom controls as
well so as to enable intellisense? If so, how?
I believe a great many people are interested in this capability both within
and outside of my organization. Please help!
~Cheers & Thanks