I am trying to use Visual Studio Installer to create an installer for my project. It's x64 project but I keep getting a compatibility error:
Error 1 targeting 'AMD64' is not compatible with the project's target platform 'x86'
I tried editing the platform of the setup project but it's greyed out!!
What am I to do?
I realized my Visual Studio 2013 is in the x86 Windows folder? ANy relation to what I am facing?
THanks all
I still don't know what was wrong but in case someone encounters this, the InstallShield LE worked smoothly...
Related
I'm using Visual Studio Community 2017 Version 15.7.1 on Windows 10 Home Version 10.0.16299 32-bit, Windows SDK Version 10.0.17134.12 and C++/WinRT Version 1.0.180505.2. When I try to create a new project using any of C++/WinRT templates, I'm getting this error message:
Error: this template attempted to load component assembly
'Microsoft.VisualStudio.Universal.TemplateWizards, Version=15.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. For more
information on this problem and how to enable this template,
please see documentation on Customizing Project Templates.
Is there an easy fix to this problem?
This error was caused by missing UWP SDK. My first installation of Visual Studio was configured for Desktop development with C++ workfload only, so UWP development workload components were missing. I added UWP development workload using Visual Studio Installer.
This error comes due to absence of UWP tools. For Visual Studio 2019, you simply have to go to Extensions>Manage Extensions>Online and search for "UWP Essentials" then download it for free. Close all Visual Studio windows and then when you open it again, the problem should be solved.
The easiest way to fix this is to install the whole UWP Essentials package. It contains a lot, but it gives you everything to fix the issue. Go to Tools > Extensions and Updates > Online and search for "UWP Essentials", and use the Visual Studio Installer to get it.
I have installed Visual Studio 2013 then installed Windows Driver Kit (WDK) 8.1. I'm using Windows 7. I already had a project which is a modified fastfat. I was building that using VS 2012 and everything was fine. But today when I try to build the same project using VS2013 I get the following error:
C:\Program Files (x86)\Windows Kits\8.1\build\WindowsDriver.common.targets(77,5): error : Unknown or unsupported property value (Vista) for TargetVersion
Note that I ran the clean procedure before doing the build.
Does anyone know what to try next?
What flavor of Visual Studio 2013 are you using (i.e., Professional, Premium or Ultimate)?
Be aware that Professional does not support Device Driver Templates. Check this by clicking on File/New/Project. Then Templates/Visual C++. If "Windows Driver" does not show up then your flavor does not support device drivers. I would try Ultimate.
can i resolve error MSB8009: .NET Framework 2.0/3.0/3.5 target the v90 platform toolset. Please make sure that Visual Studio 2008 is installed on the machine. without installing vs 2008 SP1 for visual cpp project
Your project is set to target the VC9/VS2008 toolset - if you want to build in using VC10/VS2010 without having VS2008 installed you need to target the VC10 toolset.
Open the VS2010 solution file.
Go to the project properties dialog, Configuration Properties -> General
Change Platform Toolset from v90 to v100.
You will no longer be able to build using VS2008.
I have a C++/CLI app that is built under Visual Studio 2010 but using .Net 3.5. As required, I hand edited my project file to add the TargetFrameworkVersion with a value of 3.5 and was able to build it without issue when I was in x86 (32-bit) mode. However, when I switched to build it in x64 (64-bit) mode, I got the following error:
error MSB8014: Execution path (C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\x86_amd64) could not be found.
I do have VS 2008 (9.0) installed, but there is no x86_amd64 directory under the bin folder. I tried fooling it by adding this folder (and the amd64 folder which would have failed thanks to the next line in the targets file), and then I got the error:
fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'
which I can't figure out because my project has no explicit links. I switched the C# assemblies that it interacts with to build in x64 (as opposed to any CPU) but to no avail.
FYI: Everything builds correctly in 32-bit mode. Everything also build correctly in 64 bit mode if I switch to .Net 4.0 (v100). I get the same errors building in both release and debug mode.
Any ideas would be appreciated.
If you are compiling with the "toolset" changed over from V100 to V90 on the project properties, and you have Visual Studio 2008 installed on the same development machine, just go to Control Panel, Programs and Features, select Visual Studio 2008, right-click, select Uninstall/Change, then select to add/remove f eatures, then when you are presented with a list of features, look for x64 compiler/files under Visual C++ which is not installed by default,but by clicking on the checkbox next to it, it will add the needed files.
In VS2010 it should link to C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64
You probably got configuration wrong, or imported from a vs2008 project.
Go to Configuration -> General -> Platform Toolset. make sure it's v100 (vs2010)
If that doesn't help , look at Configuration -> VC++ Directories. That's where that path is set.
You can see that it looks in $(VCInstallDir) which in your computer is set to the VS2008 path.
I built some crystal reports in VS2010, and made a setup project for it. It deploys fine on my dev machine, but I get the following error while trying to install it on the client machine.
I have googled this error for sometime and found that the VC++ 2005 redistributables are a prereq. I have added these merge modules to my setup project but I still get the same error.
I have also added .NET 4.0 as a prerequisite, and still get the same error. Anybody has any ideas?
My dev machine is running Windows 7, and I am trying to deploy it on a Windows server 2008 R2 machine.
For anyone else's reference, I ended up adding Crystal Reports Runtime Engine for .NET 4.0 as a prerequisite and just make the user download it if they dont have it installed. I also had to add a .NET 4.0 prerequisite (not the client profile) and of course the merge modules (CRRuntime_13_0.msm). If anyone has a better way of getting this to work, I am still interested. Thanks!
Try this one
http://www.businessobjects.com/jump/xi/crvs2010/us2_default.asp
I installed CRRuntime_32bit_13_0_8.msi on 64bit and finally worked
The merge modules you have added are from VC++ 2008 redistributable, not 2005.
You can download the correct redistributable from the following link:
Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
That contains the required Microsoft_VC80_CRT_x86.msm, Microsoft_VC80_MFC_x86.msm, Microsoft_VC80_ATL_x86.msm and Microsoft_VC80_OpenMP_x86.msm, as noted here.
AFAIK, There's no need to .NET 4.0 as a prerequisite, at least for Crystal Reports Runtime for VS 2010. The above redistributable added to the setup project, all that error messages are gone.
NOTE:
To add the VC++ 2005 redistributable to the VS setup project, a corresponding bootstrapper package should be added in the following folder (for VS 2010):
%Program Files%\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages
Or %ProgramFiles(x86)% folder on 64-bit Windows.
UPDATE:
To create a prerequisite bootstrapper package, see the following links (borrowed from here):
Deploying Custom made Visual Studio prerequisites using Bootstrapper Manifest Generator
Creating Bootstrapper Packages