I've installed InstallShield LE for Visual Studio 2012 and created an msi. It works fine installing on a 64 bit machine, but on a 32 bit machine I get an error "(null) is not a valid Win32 application".
My project is built to support Any CPU as the platform target.
If your machine is 64 bit, it will only make the 64 bit .msi file when you build "Any CPU". I had the same issue and found the best solution is just to use a 32 bit platform or make two separate projects and have two different installers. If you want to have both 32 bit and 64 bit .msi files in a single setup project you have to get the Pro version.
The answer to this question discuses how to do this.
Installshield 2012 : Identify 32 or 64 bit Operating system and install appropriate ActiveX control - Basic msi installer
Related
HiI want to build my solution with VS 2013 64 bits, do I have to rebuild the latest version in 64 its or I can use the 32 ???thanks
What matters is the target. If you have a project for Platform Win32, all referenced libraries must be compiled for Win32 and if you have a project for Platform x64, all referenced libraries must be compiled for x64 (and with compatible compiler settings; visual studio has several project options that when changed make the libraries incompatible). Particular variant of VS 2013 does not matter.
I have written an application that uses CR for Visual Studio. It deploys and runs fine on 32 bit systems. I want it to work on 64 bit systems too, so I ran CRRuntime_64bit_13_0_7.msi to install the redistributable.
When I select my prerequisites in VS 2012, should I see an entry for CR 64 bit? I don't.
In VS, I set the target CPU to x64 and publish (Clickonce). When I try to install it on my Win 7 64 bit system, I get an error:
Unable to install or run the application. The application requires that assembly CrystalDecisions.ReportAppServer.CommonObjectMode Version 13.0.2000.0 be installed in the Global Assembly Cache (GAC) first.
How can I deploy the 64 bit CR runtime with my application?
Thanks
Maybe there's a bug with the Service Pack 7 version of the files? Have you tried with the Service Pack 8 version that was recently released?
SAP Crystal Reports, Developer version for Microsoft Visual Studio
Is your development environment 32-bit or 64-bit? Because that might have a bit to do with it also. Installing and deploying Crystal has always been a pain (I've been working with it since version 7.0) and to introduce the complexity of 32/64-bit makes it even more fun!
Another thing to point out on that link was that you have to run the "Install executable" to get it to integrate into VS properly. When I did so, it asked me if I wanted to install the 64-bit runtime as my PC was 64-bit, did you get to this point and if so, which version did you choose?
In the app we're working on, we have a routine that inspects all assemblies in the dependencies folder and auto-loads classes with a certain attribute, but when I went to run the app targeting a 64-bit CPU (or even Any CPU) it would give me exceptions when trying to load the Crystal Reports assemblies on start-up, but it would work fine when targeting a 32-bit CPU.
Which leads me to think that perhaps they either don't have their 32/64-bitness sorted properly, or their installer isn't doing what it says it is.
I am converting some 32-bit .Net apps to x64. Enterprise Library 5 (32-bit) is used in a bunch of our apps, so I am under the impression that when we re-compile those in x64, then we will need to pull in a x64 version of EntLib. Does anyone know if that exists? I keep searching and I can't seem to find a straight answer - I find burbs about x64 configuration manager tool, but no info about a installable 64-bit version of EntLib5.
The entlib assemblies are architecture neutral. They can be loaded by either 32 or 64 bit processes with no changes.
On a 32-bit process, they'll run as 32-bit. On a 64-bit process, they'll run as 64 bits. No changes needed.
Remember, they're IL, not native code, and don't call into anything native, so there's no bitness dependencies.
Using Visual Studio, I have built an C++ application running in 32bit. It will be deployed both to 32-bit and 64-bit Windows servers. It won't be run in 64-bit mode (but rather under WoW).
Should I include both the 32-bit and 64-bit Visual C++ redistributable, and install 32bit on 32bit Windows and 64bit on 64 bit Windows, or is it enough to just install the 32bit redistributable?
It is enough to install the 32bit redistributable.
EDIT: I commented below on a misleading answer, but the answer is you only need the 32-bit redistributables, as Karel Petranek answered first.
This is not an answer. It should only be a comment, but since I don't have the required reputation for that...:
I just wanted to warn people against Ruel's provided information. No, the 64-bit Visual C++ redistributable packages don't also include the 32-bit DLLs.
I have even tested that (his) theory. I tried to run an application that requires Visual C++ 2010 32-bit redistributables and it prompted me that it needs that. I then installed the 64-bit one, and it still prompted it needed the 32 bit version of Visual C++ 2010. After installing the 32 bit one, it worked.
Why people come up with theories and provide them as answers beats me. Or maybe he was also "encouraged" by the reputation system to give not only superfluous, but also false information. Or maybe he just confused C++ with DirectX 9 redistributables (that one does install both 32-bit and 64-bit DLLs).
Both are Microsoft products, but don't let that fool you.
Your C++ application creates a 32 bits EXE, linking to 32 bits DLLs. As it happens, one or two of those DLLs are Microsoft CRT DLLs, but the OS still uses the same rules. Therefore, you don't need the 64 bits DLLs.
Compile it using /MT option and VC++ runtime library will be compiled into your exe, so you don't have to worry about distributing it.
Project > Properties > Configuration Properties > C/C++ > Code Generation > Runtime Library > Multi-threaded (/MT).
The 64-bit Visual C++ redistributable package includes both 32-bit Visual C++ redistributable and 64-bit Visual C++ redistributable.
Our development environment is all 32 bit, but our production SharePoint farms are all 64 bit. Can we just deploy the SharePoint solutions straight to the 64 bit platform, or do we need to recompile everything?
If you have the Platform Target set to "Any CPU" (which is the default) then you do not need to recompile. You can find this drop-down by going to the Build tab in the project properties. The .NET Framework is smart enough to adjust to either platform when this setting is enabled.
I'm working in the same environment that you describe with these settings and have no issues.
Edit: A good question that describes this further - Compile ASP.NET to 64 BIT.
Slightly offtopic, but if you deliver your solution files through MSI's build as a simple Visual Studio Setup Project, like we do, that's a different story. Those MSI's are 32 bits, and require a fair bit of modding to make them 64 bits compatible.
The solutions themselves, however, should pose no problem whatsoever.