Hello everyone,
I have one confusion about strongly named assembly.
Suppose I am developing a library (DLL), and other application is linked with it (reference to the library DLL), my purpose is not to make the dependent application rebuild if I do not change the interface exposed to the application.
(i.e. if I just changed the implementation of the exposed interface and keep interface the same, application developer just need to copy my new library DLL, all other changes are transparent to application, and no need to rebuild.)
My question if I made the DLL strongly named, even if I keep the exposed interface the same (just change interface implementation), the application needs to rebuild? Why?
thanks in advance,
George
Bechir BejaouiPosted Oct 31, 2008, 7:56 PM
George GeorgePosted Oct 30, 2008, 9:20 AM
Sorry I think we are talking about two things. My question is, if my exe application is referening a DLL, and the DLL is strong named. Then if the DLL is released with a new version, then the exe application has to rebuild with the new version DLL, correct? Any ways to save the rebuild step?
regards,
George
Bechir BejaouiPosted Oct 30, 2008, 7:16 AM
George GeorgePosted Oct 27, 2008, 7:33 AM
It is a pure .Net assembly. My current confusion is, support the client application is built with strongly named assembly version 1, and if I change the strongly named assembly to version 2 and deploy to client environment, and also keep interfaces used by client application the same, will there any needs or benefits for the client application to rebuild?
regards,
George
Bechir BejaouiPosted Oct 27, 2008, 7:11 AM