Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to change "output path" on Visual Studio 2012 and x64 configuration #3918

Open
wixbot opened this issue Feb 20, 2013 · 9 comments
Open

Comments

@wixbot
Copy link

wixbot commented Feb 20, 2013

The output path on the visual studio 2012 plugin can't be changed when x64 configuration are chosen (both release and debug).
Visual studio 2010 works fine and x86 configuration too.
Whatever I tried on x64 the Output path is overriden by "bin$(Platform)$(Configuration)"
Close on relaunch visual studio don't fix the problem.

Configuration :
Windows 7 Ultimate french
Visual Studio 2012 ultimate edition

Originally opened by vletoux from http://sourceforge.net/p/wix/bugs/3217/

@wixbot
Copy link
Author

wixbot commented Mar 5, 2013

The problem is due to the fact that when adding the x64 config, the project.config contains duplicates entries for x64.
(cf attachement)

How to reproduce :

  1. create a new setup project
  2. add the x64 config based on the x86 config

Workaround :
edit the project.config and remove the duplicate entries

@wixbot
Copy link
Author

wixbot commented Oct 8, 2013

Originally changed by barnson
Area changed from visual studio 2012 wix 3.7 to votive
Release changed from future to v3.x

@wixbot
Copy link
Author

wixbot commented Feb 6, 2015

I am facing this same problem in VS 2013 IDE also. Did the latest version of WiX installer addressed this bug ? Please share the update.

Originally posted by karansaini

@wixbot wixbot added this to the v3.x milestone Dec 20, 2015
@rhyous
Copy link

rhyous commented Jul 1, 2016

I can't change the platform to x64 in VS 2015 U2, Wix 3.10.2.2516

@Simon-IT
Copy link

Simon-IT commented Jan 3, 2017

Hi guys,
the problem persists through Wix 3.10.3 and Visual Studio 2015 Community Update 3. Anyone can repair it ?
Thanks all.

@VinayNunna6
Copy link

Change the configuration settings from x86 to x64 (use new option )under solution properties, that will automatically update the project property as well.

@DominikRoB
Copy link

Hey, is there any update on this?

I have a VS Solution with a handful of projects and it seems to be completely impossible to hack my way out this issue. (For smaller projects usually modifying the wix project file after adding x64 plattform works, but not this time..)

@robmen
Copy link
Member

robmen commented Oct 4, 2021

This issue is open and unassigned. That means it is waiting for someone to investigate the root problem, discuss possible solutions to that problem then implement the decided solution.

If you are interested in doing so yourself, our developer documentation provides a great checklist for getting started.

If you are not interested then you are waiting for someone else to become interested. If this issue has been open for a long time then there probably isn't much interest in this particular issue. In that case, you'll want to consider how to motivate others to fix it for you. This is a pretty good list of support options.

@NPatch
Copy link

NPatch commented Dec 8, 2021

After going to ConfigurationManager and adding a new solution platform for x64, this is the generated sln:

Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio Version 16
VisualStudioVersion = 16.0.31911.196
MinimumVisualStudioVersion = 10.0.40219.1
Project("{930C7802-8A8C-48F9-8165-68863BCCD9DD}") = "SetupProject1", "SetupProject1\SetupProject1.wixproj", "{E4AFD734-6D5A-4A39-AA93-9408405B153F}"
EndProject
Global
	GlobalSection(SolutionConfigurationPlatforms) = preSolution
		Debug|x64 = Debug|x64
		Debug|x86 = Debug|x86
		Release|x64 = Release|x64
		Release|x86 = Release|x86
	EndGlobalSection
	GlobalSection(ProjectConfigurationPlatforms) = postSolution
		{E4AFD734-6D5A-4A39-AA93-9408405B153F}.*******Debug|x64.ActiveCfg = Debug|x86*******
		{E4AFD734-6D5A-4A39-AA93-9408405B153F}.Debug|x86.ActiveCfg = Debug|x86
		{E4AFD734-6D5A-4A39-AA93-9408405B153F}.Debug|x86.Build.0 = Debug|x86
		{E4AFD734-6D5A-4A39-AA93-9408405B153F}.*******Release|x64.ActiveCfg = Release|x86*******
		{E4AFD734-6D5A-4A39-AA93-9408405B153F}.Release|x86.ActiveCfg = Release|x86
		{E4AFD734-6D5A-4A39-AA93-9408405B153F}.Release|x86.Build.0 = Release|x86
	EndGlobalSection
	GlobalSection(SolutionProperties) = preSolution
		HideSolutionNode = FALSE
	EndGlobalSection
	GlobalSection(ExtensibilityGlobals) = postSolution
		SolutionGuid = {77DEDAAC-E6D5-4243-AA6C-8D4D94C9A326}
	EndGlobalSection
EndGlobal

In the same solution, I have a bootstrapper, a classic msi setup proj and a regular csproj. After trying to create the solution and project platforms and try to build with the x64 solution platform, the csproj compiles in x64 properly, while the other two in x86.
In the generated solution, I notice that the csproj has correct mappings, whereas the bootstrapper and the msi project , like the bold parts(wrapped in *******) in the above MSBuild snippet, have that x64->x86 mapping which probably forces the wrong project platform, through the Votive extension.

FWIW, before stumbling upon the sln, I modified the wixproj to use by default the x64 platform (first PropertyGroup) and then made sure to just leave the PropertyGroups for x64 which set the output paths and that worked even with the wrong sln.

@robmen robmen modified the milestones: v3.x, v.Votive Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants