omposite control maintainence

In order to maintain my composite controls I will need to modify them from
time to time. Are there special requirements for composite controls
development to make sure that any change to composite control will be
reflected on any page the control has been used on?On Sun, 29 Aug 2004 07:39:10 -0500, Mark Goldin <markgoldin@.comcast.net>
wrote:

> In order to maintain my composite controls I will need to modify them
> from
> time to time. Are there special requirements for composite controls
> development to make sure that any change to composite control will be
> reflected on any page the control has been used on?
>
Is versioning what you're looking for? Any new version you should update
your AssemblyInfo file as I assume you're distributing them as a dll.
Then the user code will compile against the version they want...they can
update when they want.
Craig Deelsnyder
Microsoft MVP - ASP/ASP.NET
Here is a problem I have.
I am modifying my custom control during a day many times.
After every modification I have to remove the control from the form, remove
reference to a dll and place control back to form in order to pick up the
changes.
Is that because I am not implementing versioning?
"Craig Deelsnyder" <cdeelsny@.no_spam_4_meyahoo.com> wrote in message
news:opsdilxui475dg5d@.g51y101...
> On Sun, 29 Aug 2004 07:39:10 -0500, Mark Goldin <markgoldin@.comcast.net>
> wrote:
>
> Is versioning what you're looking for? Any new version you should update
> your AssemblyInfo file as I assume you're distributing them as a dll.
> Then the user code will compile against the version they want...they can
> update when they want.
> --
> Craig Deelsnyder
> Microsoft MVP - ASP/ASP.NET