I want my <asp:

[Chris]

By putting custom controls in the GAC, I can do a <% Register
TagPrefix="..." assembly="MyAssembly, version=1.0.0, culture=neutral,
PublicKeyToken=1234567890" namespace="MyNameSpace %>.

This is OK, I guess, but what if I have a 2 or 3 sites consisting of 1000
pages, each with that Register directive, and I build a new version of
MyAssembly? I could do a search and replace in all files but why can't I
make these controls available in the same way that the <asp:xxx> controls
are available?

What would be a better method? I've seen lots suggestions on the web and in
this newsgroup but they're all pretty flimsy and user-unfriendly. There has
to be a good official way of doing this!

Regards
Chris

 

[Jacob Yang [MSFT]]

Hi Chris,

Based on my research and experience, I would like to share the following
information with you:

1. When you build a new version of "MyAssembly" and add it to the GAC, the
old version of "MyAssembly" is still in the GAC. So all the old pages can
still use the old version of "MyAssembly". We only need to tell the new
page to use the new version of "MyAssembly".

2. If you want all the old pages to use the new version of "MyAssembly" in
the GAC, please try to remove the old version of "MyAssembly" from the GAC
and test this issue.

3. If the step 2 does not work and you do not want to change each old page
to use the new version of "MyAssembly", the work around is not adding
"MyAssembly" to the GAC . Please refer to the following Knwoledge Base
article for this issue:

HOW TO: Register an Assembly in a WebForm to Use a Custom Control
http://support.microsoft.com/default.aspx?scid=kb;en-us;321749

Does it answer your question? If I have misunderstood your concern, please
feel free to let me know.

Best regards,

Jacob Yang
Microsoft Online Partner Support
<MCSD>
Get Secure! ¨C www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.