some are OS specific and some are platform specific and some are both.Ĭrystal Reports runtime has dependencies on both depending on the starting point due to having to support 32 bit DB clients and printer drivers and at the same time handle the development in the. I believe this is true for any program these days, when you go to any app support site you'll typically find a 32 and a 64 bit version, print drivers, video card drivers etc. If it detects a 64 bit OS then it tries to install the 64 bit runtime only even if you have compiled your app to run in x86 mode only it obviously will fail to start, same is true forĪ 32 bit app that doesn't include the 32 runtime and only the 64 bit dependencies. I don't know the exact reason but I believe it's the way MSIExec works. I do the same thing as Gary when things don't work as expected. I understand it also but it's not always our fault and until the reason is known it bugs me when anyone assumes why. You almost double your distribution size.
I'm sure if you set your Project to 圆4 only then 32 bit redist is not required. Developing on a 32 bit OS it's not a problem.Īs for deploying, yes, if you are not going to set the platform and the app compiles for both then you do need to distribute both 32 and 64 bit runtime. There may be a way to change the New Default Project settings within VS but if not then nothing CR can do nothing to force the settings to change. When you create a new project you have the Option to select the destination Framework but not the bit version and VS assumes if you are using it on a 64 bit OS then An圜PU is Long story, but bottom line is this is a free product and SAP's Resources focused on the BusinessObjects Enterprise 4.0 product andĪs for the default setting within Projects that is a VS configuration question. Go through the beta testing process of VS and things like this were not caught in the CR Beta testing and resolved before GA.
For what ever reason with the "powers that be" CR was not included with the VS 2010 install, I believe it was due to SAP not being ready to integrate into VS before it went GA and there may be other reasons also.
0 kommentar(er)
