locked
Incrementally versioning assemblies and having your application still work... RRS feed

  • Question

  • If we increment our assembly version each build, all string references to it seem to break, for example an aspx page needs to reference dlls by their version number, the aspx will work today but not tomorrow, because tomorrow will have a different version. I've read somewhere theres ways for the CLR to load dlls by major and minor version, and always take the latest build/revision. Is this true?

    Thanks!
    Monday, March 9, 2009 8:32 PM

Answers

  • 2 assemblies with the same name and PKT, but different assembly versions are different. You can explicitly mark one compatible with the other by using assembly redirection. See more details and links in this thread.

    -Karel
    • Marked as answer by Zhi-Xin Ye Monday, March 16, 2009 10:20 AM
    Monday, March 9, 2009 10:30 PM