«

We are clearly going about this the wrong way so before we get too far I
would like some advice.

We have all common assemblies like our page base class etc located on our
Dev server.

We reference them in all our applications with Copy Local set to trued

We then publish them to the production server for example so each asp.net
app has a copy of the common assembly in the bin directory.

This is of course leaving us with the problem of having to replace the
assembly in every bin directory when a change is made.

What is the best practice to avoid this issue?

Thanks a million,

Jason MacKenzie

Hi Jason,

I'd say the easiest solution is to strong name the assemblies and put them
into the GAC where ever app would find them. You could probably call the
gacutil with a batch file to make the process efficient:

http://msdn.microsoft.com/library/de...cutil_exe_.asp

Ken

"Jason MacKenzie" <> wrote in message
news:Oy5Z%...
> We are clearly going about this the wrong way so before we get too far I
> would like some advice.
>
> We have all common assemblies like our page base class etc located on our
> Dev server.
>
> We reference them in all our applications with Copy Local set to trued
>
> We then publish them to the production server for example so each asp.net
> app has a copy of the common assembly in the bin directory.
>
> This is of course leaving us with the problem of having to replace the
> assembly in every bin directory when a change is made.
>
> What is the best practice to avoid this issue?
>
> Thanks a million,
>
> Jason MacKenzie
>