Avoiding new references

  • Thread starter Thread starter D Browne
  • Start date Start date
D

D Browne

This is probably going to be an obvious answer for some, but I'm just
looking for directions or where to look or read. How can you make an
application that references a specific file ... say foo1.2 ... not break
when foo1.3 is released.

For example, I have an application that uses a commercial available class
say V.1.0 that has a function called getColor, then the vendor releases V1.1
that fixes a bug in getColor. How could I write the application so I could
just add V1.1 in the apps folder without having to recompile the entire
application? The assembly fails because it is looking for V.1.0
 
That's exactly what the issue was. The third party control was defaulting to
specific version to true.
 
Too early... same problems


Let me see if I can explain better. We created an application using Acme's
Superbar.dll v3.0. The reference was set to specific version:false. The
application works fine.

Acme releases a hotfix called Superbar.dll v3.5. The new component is added
to the applications working folder. Now the application errors, looking for
v3.0.

Is there something I'm missing?
 
Back
Top