dpanattoni
IS-IT--Management
I might have misunderstood the purpose of the GAC. Please correct me.
My thoughts of it were that I could create a library (dll) file and put it into the GAC. Then I could write other applications that used that library. If I made changes to the library, I could make those changes, update the GAC and all of the existing programs that needed that library would then be able to use the updated library without the need for rebuilding.
I have been able to create libraries and update the GAC, but I still have to rebuild any application that uses that library if the library is changed. Am I missing something or is this the way it needs to be done? If this is the way it is supposed to be done, where is the advantage to using the GAC, I might just as well have skipped the GAC part since I can already share libraries by referencing them from within the application.
By the way, I'm using VS.net and C#.
Thanks in advance.
DP
My thoughts of it were that I could create a library (dll) file and put it into the GAC. Then I could write other applications that used that library. If I made changes to the library, I could make those changes, update the GAC and all of the existing programs that needed that library would then be able to use the updated library without the need for rebuilding.
I have been able to create libraries and update the GAC, but I still have to rebuild any application that uses that library if the library is changed. Am I missing something or is this the way it needs to be done? If this is the way it is supposed to be done, where is the advantage to using the GAC, I might just as well have skipped the GAC part since I can already share libraries by referencing them from within the application.
By the way, I'm using VS.net and C#.
Thanks in advance.
DP