A developer company sends dlls to the client. Some client is not happy current functionality, so request some modification. Developer made some changes and send new dll to all clients. Some client is happy with old version, tell me minimal change to so that neither clients get affected?
Answer / Nitesh Kumar Verma
To allow both clients to use either the updated or original DLL without affecting each other, you can implement a versioning strategy using namespaces and assembly versions. Here's an example for C#:nn```csharpn// Original namespace and assembly versionn[assembly: AssemblyVersion("1.0.0.0")]
namespace OriginalNamespace {n // Your original code heren}nn// Updated namespace and assembly versionn[assembly: AssemblyVersion("2.0.0.0")]
namespace UpdatedNamespace {n // Your updated code heren}nn// In your application, import the desired namespace based on client requirements:nusing OriginalNamespace; // For original functionalitynusing UpdatedNamespace; // For updated functionality
| Is This Answer Correct ? | 0 Yes | 0 No |
What are Sessions?
What is a serviced component?
What is the difference between Server.Transfer and Response.Redirect?
Explain what is an anonymous method and how is it different from a lambda expression?
Is .net an object oriented language? What are their components?
What is Event - Delegate? clear syntax for writing a event delegate
What is the purpose of enumerable class in .net?
What are Satellite Assemblies? How you will create this? How will you get the different language strings?
What is a .DLL and .EXE files called in .NET?
Is atl redundant in the .net world?
Please explain what inheritance is, and why it's important?
What is finalize method in .net?