.NET and Binary compatibility
Visual Basic
1
Posts
1
Posters
0
Views
1
Watching
-
In a few months time I have to develop a DLL(s) to contain common code which our company will share across many projects. The roll out of this DLL could be problematic, and I dont want to get into lots of discussions about 'design it first then code it' coz this is the real world and we can't afford to work like that right now. To live we have to code! hehe Well, if I have my DLL(s) released out there and add a new function does this break binary compatibility in .NET. Does binary compatibility even exist in assemblies still? I would be happy to release DLL's in incremental stages if I know that I wont break things just by adding new functions and objects. Any experiences and stuff would be really appreciate. Thanks Nursey