Re: Declaratively using custom controls from the GAC

My thinking is that if you're putting something in the GAC, it is stable and is 
not likely to change on a frequent basis.  If your assembly is still undergoing 
development, then you need to either add this assembly's project to your 
primary application's solution or you need to place the assembly DLL in the 
application's bin directory.  This doesn't have to be permanent; only until you 
have your custom control assembly stable.

Christopher Reed
Web Applications Supervisor
Information Technology
City of Lubbock
creed@xxxxxxxxxxxxxxxxxxxxx
"The oxen are slow, but the earth is patient."

>>> RMcClure@xxxxxxxxx 3:17:49 PM 6/23/2005 >>>
I have some custom controls that will be used by multiple web apps.  So I 
placed them in an assembly that installs in the GAC.  If I want to use the 
custom controls declaratively, I need to add something like the following 
directive to my page:

<%@ Register TagPrefix="cc2" Namespace="SomeCompany.Web.UI.WebControls" 
Assembly="SomeCompany.Web, Version=1.0.0.0, Culture=neutral, 
PublicKeyToken=1234567890123456" %>

The problem is that the version binding happens at code writing time. If the 
version of the SomeCompany.Web assembly changes, I need to change the aspx file 
by hand.

However, if you use the custom controls dynamically (from the code behind 
page), then the version binding happens at compile time.  That's the behavior I 
want for my declarative usage as well.  Somehow this
behavior happens for the System.Web assembly. I don't have to have a Register 
directive for the System.Web assembly and the version binding happens at 
compile time.

This is especially problematic where you have nightly builds that auto 
increment the version numbers.

Anyone else come across this annoyance?  Is there some way to still use the 
controls declaratively without specifying the version at code writing time?

Thanks,

Russ

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com