Uploading a new DLL to the GAC

  • Thread starter Thread starter Scott Vercuski
  • Start date Start date
S

Scott Vercuski

Everyone,

I've run into a problem using the GAC. I've created a DLL and
put it in the GAC on our server. I've also created a webpage and
referenced that same DLL with the "Copy Local" set to false. I run
the page and things do what they're supposed to do. When I make a
change to the DLL and upload it. I can't get the website to reference
the new DLL. I've tried recompiling, removing from the GAC, etc. ...
everything I can think of and it still won't recognize the new DLL.
Am I doing something wrong or missing some vital step?

Thank you in advance for any help
Scott Vercuski
(e-mail address removed)
 
Could be that the web page reference is to a specific version of your DLL,
and you've left the assembly version in your DLL as 1.0.* (assemblyinfo
file) , and every time you build it creates a new version.
 
Phil,

I did leave my version as 1.0.* and I set the "Enable Incremental
Build" under the project property optimizations tab. Should I have
that turned off instead? I've honestly never used this option before.
When I re-register my DLL it doesn't increment the version number in
the GAC.

Thank you for your reply,
Scott Vercuski
(e-mail address removed)

Phil Wilson said:
Could be that the web page reference is to a specific version of your DLL,
and you've left the assembly version in your DLL as 1.0.* (assemblyinfo
file) , and every time you build it creates a new version.
--
Phil Wilson [MVP Windows Installer]
----
Scott Vercuski said:
Everyone,

I've run into a problem using the GAC. I've created a DLL and
put it in the GAC on our server. I've also created a webpage and
referenced that same DLL with the "Copy Local" set to false. I run
the page and things do what they're supposed to do. When I make a
change to the DLL and upload it. I can't get the website to reference
the new DLL. I've tried recompiling, removing from the GAC, etc. ...
everything I can think of and it still won't recognize the new DLL.
Am I doing something wrong or missing some vital step?

Thank you in advance for any help
Scott Vercuski
(e-mail address removed)
 
If you were building and installing everything in your project at the same
time it wouldn't matter, but you have code out there that's bound to a
specific assemblyversion and strong name of the assembly so you need to
build a new version that matches what the existing code is expecting. The
other alternative is a publisher policy that redirects client programs from
the version they're looking for to the version you want them to use. I'm not
sure what you mean by "doesn't increment the version in the GAC", but
remember that multiple versions can exist side-by-side in the GAC (look at
the 1.0 and 1.1 framework files all in the GAC at the same time) so when you
put your new DLL in the GAC I'd assume that you're not replacing the old one
at all, just adding another with the same name but different
assemblyversion.
--
Phil Wilson [MVP Windows Installer]
----
Scott Vercuski said:
Phil,

I did leave my version as 1.0.* and I set the "Enable Incremental
Build" under the project property optimizations tab. Should I have
that turned off instead? I've honestly never used this option before.
When I re-register my DLL it doesn't increment the version number in
the GAC.

Thank you for your reply,
Scott Vercuski
(e-mail address removed)

"Phil Wilson" <[email protected]> wrote in message
Could be that the web page reference is to a specific version of your DLL,
and you've left the assembly version in your DLL as 1.0.* (assemblyinfo
file) , and every time you build it creates a new version.
--
Phil Wilson [MVP Windows Installer]
----
Scott Vercuski said:
Everyone,

I've run into a problem using the GAC. I've created a DLL and
put it in the GAC on our server. I've also created a webpage and
referenced that same DLL with the "Copy Local" set to false. I run
the page and things do what they're supposed to do. When I make a
change to the DLL and upload it. I can't get the website to reference
the new DLL. I've tried recompiling, removing from the GAC, etc. ...
everything I can think of and it still won't recognize the new DLL.
Am I doing something wrong or missing some vital step?

Thank you in advance for any help
Scott Vercuski
(e-mail address removed)
 
Back
Top