new to deploying .dll to gac

[Guest]

hey all,

let's say i develop a custom control and want to deploy to the gac. i use
the strong name utility and move it to the gac on the web server.

now when other developers develop with my custom control they'll need that
custom control on their local development environment, and then referenced to
the project (please correct if no right so far). when they reference the
control it automatically adds it to the bin. when they're ready to deploy
after they've compiled in release mode, will they have to go in the bin and
delete the dll to the custom control so the version in the gac of the web
server will be used?

thanks,
rodchar

 

[Phill. W]

let's say i develop a custom control and want to deploy to the gac. i use
the strong name utility and move it to the gac on the web server.
now when other developers develop with my custom control they'll
need that custom control on their local development environment,
and then referenced to the project

BZZZZ ;-)
They'll need the DLL, "registered" in their local GAC. Then, they
reference the DLL; they shouldn't need the custom control's Project
at all.

when they reference the control it automatically adds it to the bin.

Not if it's installed in the GAC.

when they're ready to deploy after they've compiled in release mode,
will they have to go in the bin and delete the dll to the custom control
so the version in the gac of the web server will be used?

I've found that once a Project has got a "taste" for having a DLL locally,
it's damned difficult to presuade it to work any other way. As a result,
I have an /awful/ lot of stuff in the GAC, just to make sure I *never*
get these CopyLocal problems.

HTH,
Phill W.