Page 2 of 2
Different companies Stimulsoft DLLs are conflicting with each other
Posted: Thu Oct 18, 2007 7:02 pm
by lcruiser
Just a suggestion, I recompile my apps and don't have the need to use this, however I think it may solve the need to recompile.
Add the follwing section to your App.config file:
Code: Select all
add the rest of the report assembly here ...
I hope it helps.
Different companies Stimulsoft DLLs are conflicting with each other
Posted: Fri Oct 19, 2007 3:20 am
by Vital
Fabio wrote:But now i must recompile my dlls for each new Stimulreport "pre-release" version, because (example) my dlls were compiled with 2007.3.0.0 version (in Stimulsoft references i set "SpecificVersion=False") and now that i have put in my application directory the new 2007.3.12.0 dlls (without recompiling my dlls) i receive the following error:
"System.IO.FileLoadException: Could not load file or assembly 'Stimulsoft.Report, Version=2007.3.0.0, Culture=neutral, PublicKeyToken=ebe6666cba19647a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)"
The error is thrown because my dll is compiled against 2007.3.0.0 version (note again that in Stimulsoft references i set "SpecificVersion=False" - actually i don't know if it's influencing something) while now in my app dir is present only 2007.3.12.0 version.
Anyway, your choice to change the version at each build is ok for me, because this solves the problem stated at the beginning of the thread. My fault is that i don't want to deal with GAC so i'm not able to have a side-by-side situation.
If someone has some suggestion please post here.
Thanks.
This is why we don't make changes of our code early.
Thank you.
Different companies Stimulsoft DLLs are conflicting with each other
Posted: Sat Oct 20, 2007 4:38 am
by Fabio Pagano
Edward wrote:I think that Fabio suggested a suitable decision of the issue but this solution requires rebuilding the earlier version of the Application as well.
I don't agree. If i put Stimulsoft dlls in my application directory, if new prerelease versions don't change build number (eg. are all at 2007.3.0.0 just like it was before) there is no need to recompile my sources.
In previous scenario i only needed to put new Stimulsoft dlls in my application dir without recompiling anything, neither changing app.config files as lcruiser suggested (lcruiser: the solution is good but i'm forced to change many app.config files anytime).
This was just to make things clearer: as i have stated before i agree that each prerelease has his own build number (this behavior is adopted by other third party components vendors that i use).
So i'll deal with recompiling, no big problem at all.
Thanks.