As I told you Rushi, in a other thread ASP and DLL binary compatibility don't have to much in common. IF the DLL is corectly registered (and other version corectly unregistered) and corectly added to MTS or COM+ libraries (if the case) you don't need to worry about binary compatibility.
Here is my approach when working with one DLL and ASP.
On development machine I compile each time the DLL without binary compatibility (as I mentioned I'm using only one DLL****)
When I bring it to production, I copy the DLL on the same directory path as in development, register, add to MTS or COM+ and that's it.
When I have to replace it with a new dll first I delete the component from MTS or COM+,then I unregister the DLL, restart the IIS, copy the new DLL over the old one, register it and added to MTS or COM+.
That's it.
**** From my opinion you should be carefully with binary compatibility only when you reference in a dll(#1) another dll(#2).
If you compile #2 without binary compatibility the #1 will not work anymore. So you have to open the project for #1 and compile it again with binary compatibility.
Hope you understand what I worte here
