Different companies Stimulsoft DLLs are conflicting with each other
-
- Posts: 62
- Joined: Mon Dec 11, 2006 1:43 pm
- Location: U.S.A.
Different companies Stimulsoft DLLs are conflicting with each other
We have a customer that is using Stimulsoft as part of our product (Cherwell Service Desk) as well as someone else's product (eRoom client). Our customer cannot run our reports without getting this error: "a get or set accessor must be provided".
Our DLLs were March 29th and the other product's DLLs were August 29th. However, both sets of DLLs are marked as file version 2007.2.0.0. We do not install to the GAC, but I'm guessing the other product does.
What can I do about this? It seems like each new set of DLLs should have the file version incremented. Is there a final 2.0 version that we should all be using?
Thanks,
Sandy
Our DLLs were March 29th and the other product's DLLs were August 29th. However, both sets of DLLs are marked as file version 2007.2.0.0. We do not install to the GAC, but I'm guessing the other product does.
What can I do about this? It seems like each new set of DLLs should have the file version incremented. Is there a final 2.0 version that we should all be using?
Thanks,
Sandy
Different companies Stimulsoft DLLs are conflicting with each other
I've asked that a while ago and the answer was no, they couldn't do it.
Marco
Marco
-
- Posts: 62
- Joined: Mon Dec 11, 2006 1:43 pm
- Location: U.S.A.
Different companies Stimulsoft DLLs are conflicting with each other
This is unacceptable. It means that if 2 companies use Stimulsoft, but they each ship different version 2.0 DLLs, one product may not work (this is what has happened to us). This MUST be addressed. Or, Stimulsoft needs to tell everyone that they must ship the final 2.0 version only. And, then, no one can ship the 3.0 until the final version is released.
Different companies Stimulsoft DLLs are conflicting with each other
Agreed that this is unacceptable and that it MUST be addressed.Sandy wrote:This is unacceptable. It means that if 2 companies use Stimulsoft, but they each ship different version 2.0 DLLs, one product may not work (this is what has happened to us). This MUST be addressed. Or, Stimulsoft needs to tell everyone that they must ship the final 2.0 version only. And, then, no one can ship the 3.0 until the final version is released.
The other option is that Stimulsoft insist that Stimulreports is never installed into the GAC.
Different companies Stimulsoft DLLs are conflicting with each other
We try returning to this problem and will try to solve it anyway. We will inform you about results.
Thank you.
Thank you.
- Fabio Pagano
- Posts: 355
- Joined: Mon Apr 16, 2007 12:38 pm
- Location: Bari (Italy)
Different companies Stimulsoft DLLs are conflicting with each other
Sorry if i'm missing something, but if you distribute your dlls in your application directory, aren't they used instead of the ones in the GAC?
Different companies Stimulsoft DLLs are conflicting with each other
I think that Fabio suggested a suitable decision of the issue but this solution requires rebuilding the earlier version of the Application as well.
From the next prerelease build (we expect it today) this issue will be solved. So now each prerelease build will have a unique number and can be installed in the GAC in the same time.
Thanks, Marco for the suggestion you'd made!
Thank you.
From the next prerelease build (we expect it today) this issue will be solved. So now each prerelease build will have a unique number and can be installed in the GAC in the same time.
Thanks, Marco for the suggestion you'd made!
Thank you.
-
- Posts: 62
- Joined: Mon Dec 11, 2006 1:43 pm
- Location: U.S.A.
Different companies Stimulsoft DLLs are conflicting with each other
Thank you for fixing this so quickly. You guys are wonderful!
- Fabio Pagano
- Posts: 355
- Joined: Mon Apr 16, 2007 12:38 pm
- Location: Bari (Italy)
Different companies Stimulsoft DLLs are conflicting with each other
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.
"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.
Different companies Stimulsoft DLLs are conflicting with each other
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:
I hope it helps.
Add the follwing section to your App.config file:
Code: Select all
add the rest of the report assembly here ...