![]() If you create good program code that comes after standard idioms and recommended practices, including 64-little bit support afterwards (if it actually does confirm to become of some advantage for your case) would be a fairly trivial procedure. Since you'll only be constructing a individual binary, this would greatly simplify advancement and submission efforts, not just in conditions of figuring out which DLLs to reference, but furthermore the quantity of code you require to test and the distribution procedure itself. So to perform this, you just established your task to target times86 platforms, and benchmark 32-bit DLLs exclusively. ![]() Visual Studio itself is definitely an excellent instance: it's nevertheless 32-bit code, but runs fine actually on 64-bit versions of Home windows, thanks to Now64. Plenty of programs are usually deployed this method. It'beds entirely seamless, and there are virtually no compatibility issues to talk of. This is usually because all 64-little bit variations of Home windows include a exclusive subsystem that runs 32-little bit code. You can build and deliver only a 32-bit edition (back button86) and it will still run on all machines, regardless of whether they are usually operating a 32-little bit or 64-bit version of Home windows. Many line-of-business programs (which I can assume is what you're building, since you're also generating reviews from it) perform not actually advantage from getting 64-little bit. I understand this isn'testosterone levels officially an solution to your issue, but since it nevertheless continues to be unanswered also after having fixed a bounty, I thought I might suggest it in any case You might ré-consider whether yóu really need a 64-little bit version of your application. Wish that helps some of you men out right now there. Upgrade: What I did had been to reference the times86 dlls when creating, and install the a86 redistributable edition of crystal reviews on all my deployment machines, irrespective of its structures. net Framework 2.0 X64 Redistributable Package (64 Bit)Ĭommon SAP BusinessObjects Business XI 4.0 win32x86 The app that I'meters going to deploy can be deployed on both 32-bit and 64-bit Personal computers, so which CrystaI Reports DLLs shouId I research? Or do I need to possess 2 separate solutions, a single with the times86 dlls referenced, and the additional with back button64? Typical SAP BusinessObjects Enterprise XI 4.0 win64圆4. ![]() After setting up Crystal Reports fór VS 2012, I observed there are 2 main folders. I'm currently making use of VS 2012 on a 64-bit PC, using Crystal Reports fór VS 2012. net Framework 2.0 X64 Redistributable Package (64 Bit) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |