Add the follwing section to your App.config file:
Code: Select all
add the rest of the report assembly here ...
Code: Select all
add the rest of the report assembly here ...
This is why we don't make changes of our code early.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.
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.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.