N
Nicholas
My associate made this claim during a meeting about which I have
doubts - perhaps someone would clarify this:
(1) He compiles his C#.Net 1.1 DLL and installs it to the GAC.
(2) Other applications (.Net framework) use his DLL.
(3) He makes a slight change to a method and recompiles his DLL,
installing the update to the GAC.
(4) All dependant applications break and must be first recompiled to
use his DLL.
(5) He claims .Net is junk an breaks because the CRC of his newly
recompiled DLL changed.
This seems to be at odds with the .Net framework - I recall that VB
classic had "project compatibility" and "binary compatibility" - is
this a similar issue with C#?
doubts - perhaps someone would clarify this:
(1) He compiles his C#.Net 1.1 DLL and installs it to the GAC.
(2) Other applications (.Net framework) use his DLL.
(3) He makes a slight change to a method and recompiles his DLL,
installing the update to the GAC.
(4) All dependant applications break and must be first recompiled to
use his DLL.
(5) He claims .Net is junk an breaks because the CRC of his newly
recompiled DLL changed.
This seems to be at odds with the .Net framework - I recall that VB
classic had "project compatibility" and "binary compatibility" - is
this a similar issue with C#?