Re: [WiX-users] In .wixproj, default Build Configuration ignored or not settable?
This is an old thread, but I finally got around to figuring out an answer. There may be a Votive bug, or a VisualStudio bug/feature. Maybe you guys can tell me. When you fire up VisualStudio (I'm using 2010) and hit Build/F6 it does not, per se, build the Default Build Configuration (the one that builds when running msbuild from command line). It builds whichever configuration comes first in the UI drop-down, based on whatever sorting that uses. You'll want to delete your .suo file to verify this, because it saves the last used build configuration. On a fresh source-control checkout, or after deleting unversioned files, the .suo file doesn't exist, so it's important that the default configuration be what we expect. In my case, Debug SU (note the space) builds by default because it comes before Debug in the list. If I remove the space, then DebugSU comes after Debug, and Debug builds first. In either case, command-line msbuild builds Debug. I did try adjusting the order of things in the .sln file and it didn't make a difference. This does appear to be based on UI sorting. It seems like it should build the Default Build Configuration - the same as when building via command line - when I launch the IDE and hit Build. Should I log a Votvie bug about this, or do you think it's VisualStudio's doing? Thanks, - John Burak -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/In-wixproj-default-Build-Configuration-ignored-or-not-settable-tp7565859p7580890.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] In .wixproj, default Build Configuration ignored or not settable?
Are you not specifying the build configuration you wish to build? -Original Message- From: john.burak [mailto:john.bu...@telvent.com] Sent: Thursday, September 27, 2012 12:08 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] In .wixproj, default Build Configuration ignored or not settable? This is an old thread, but I finally got around to figuring out an answer. There may be a Votive bug, or a VisualStudio bug/feature. Maybe you guys can tell me. When you fire up VisualStudio (I'm using 2010) and hit Build/F6 it does not, per se, build the Default Build Configuration (the one that builds when running msbuild from command line). It builds whichever configuration comes first in the UI drop-down, based on whatever sorting that uses. You'll want to delete your .suo file to verify this, because it saves the last used build configuration. On a fresh source-control checkout, or after deleting unversioned files, the .suo file doesn't exist, so it's important that the default configuration be what we expect. In my case, Debug SU (note the space) builds by default because it comes before Debug in the list. If I remove the space, then DebugSU comes after Debug, and Debug builds first. In either case, command-line msbuild builds Debug. I did try adjusting the order of things in the .sln file and it didn't make a difference. This does appear to be based on UI sorting. It seems like it should build the Default Build Configuration - the same as when building via command line - when I launch the IDE and hit Build. Should I log a Votvie bug about this, or do you think it's VisualStudio's doing? Thanks, - John Burak -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/In-wixproj-default-Build-Configuration-ignored-or-not-settable-tp7565859p7580890.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] In .wixproj, default Build Configuration ignored or not settable?
The original issue was that we wanted to specify which configuration builds by default after launching the IDE with no preexisting .suo file. Turns out this is dictated by the names of the configurations in the solution. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/In-wixproj-default-Build-Configuration-ignored-or-not-settable-tp7565859p7580896.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] In .wixproj, default Build Configuration ignored or not settable?
There is a bug open that the solution builds don't work quite right ( http://sourceforge.net/p/wix/bugs/2993/). My understanding is that this is an issue with MPF provided by Visual Studio and no one has tracked down how to fix it in Votive. Your issue sounds like it might be related. On Thu, Sep 27, 2012 at 11:48 AM, john.burak john.bu...@telvent.com wrote: The original issue was that we wanted to specify which configuration builds by default after launching the IDE with no preexisting .suo file. Turns out this is dictated by the names of the configurations in the solution. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/In-wixproj-default-Build-Configuration-ignored-or-not-settable-tp7565859p7580896.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching http://RobMensching.com LLC -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] In .wixproj, default Build Configuration ignored or not settable?
If you are building the .wixproj directly then the defaults specified in the .wixproj should be true but the environment might have a say. If you are building the .sln that contains the .wixproj then MSBuild will choose a Configuration|Platform dependent on the .sln. You'll want to investigate the solution Configuration|Platform to make sure the correct project Configuration|Platform is selected. Again the environment might have a say in choosing the Configuration|Platform at the solution level when it is not specified. We've ran into scenarios where the default Configuration|Platform chosen varied depending on whether you are calling MSBuild without using the vsvars32.bat to configure the environment or whether you are running in an environment configured by vsvars32.bat or one of the other batch scripts delivered by Visual Studio. For example, the Visual Studio Command Prompt (2010) chooses different defaults for Configuration|Platform than Visual Studio x64 Win64 Command Prompt (2010). If you are running this from a script then my suggestion is that you always specify the Configuration|Platform in your script and specify the defaults you want in your script. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Monday, May 21, 2012 10:13 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] In .wixproj, default Build Configuration ignored or not settable? A verbose MSBuild log file should show you how the property values are changing. If not, I've found sprinkling Message tasks in the MSBuild files is often the fastest way to see why values are not what I want them to be. Just had to do that today to fix the bundle signing bug. smile/ On Fri, May 18, 2012 at 10:45 AM, john.burak john.bu...@telvent.com wrote: It's my understanding that with MSBuild, the configuration and platform used when none are specified is defined near the top of the project file in the elements with blank conditions, like this: ?xml version=1.0 encoding=utf-8? Project ToolsVersion=4.0 DefaultTargets=Build xmlns=http://schemas.microsoft.com/developer/msbuild/2003; PropertyGroup *Configuration Condition= '$(Configuration)' == '' Debug/Configuration Platform Condition= '$(Platform)' == '' x86/Platform * This doesn't seem to be happening for a wixproj I have. I've added two new build configurations, and it keeps building one of those by default, called Debug SU. I want it to build Debug by default. I'm calling MSBuild from a script. Does anyone know how to have a specific configuration used by default when one isn't specified to MSBuild? I could add logic to check for this one solution and pass in a specific configuration, but that's a bit ugly if there is supposed to be a settable default. Thanks, - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/In-wixpr oj-default-Build-Configuration-ignored-or-not-settable-tp7565859.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list
Re: [WiX-users] In .wixproj, default Build Configuration ignored or not settable?
A verbose MSBuild log file should show you how the property values are changing. If not, I've found sprinkling Message tasks in the MSBuild files is often the fastest way to see why values are not what I want them to be. Just had to do that today to fix the bundle signing bug. smile/ On Fri, May 18, 2012 at 10:45 AM, john.burak john.bu...@telvent.com wrote: It's my understanding that with MSBuild, the configuration and platform used when none are specified is defined near the top of the project file in the elements with blank conditions, like this: ?xml version=1.0 encoding=utf-8? Project ToolsVersion=4.0 DefaultTargets=Build xmlns=http://schemas.microsoft.com/developer/msbuild/2003; PropertyGroup *Configuration Condition= '$(Configuration)' == '' Debug/Configuration Platform Condition= '$(Platform)' == '' x86/Platform * This doesn't seem to be happening for a wixproj I have. I've added two new build configurations, and it keeps building one of those by default, called Debug SU. I want it to build Debug by default. I'm calling MSBuild from a script. Does anyone know how to have a specific configuration used by default when one isn't specified to MSBuild? I could add logic to check for this one solution and pass in a specific configuration, but that's a bit ugly if there is supposed to be a settable default. Thanks, - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/In-wixproj-default-Build-Configuration-ignored-or-not-settable-tp7565859.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] In .wixproj, default Build Configuration ignored or not settable?
It's my understanding that with MSBuild, the configuration and platform used when none are specified is defined near the top of the project file in the elements with blank conditions, like this: ?xml version=1.0 encoding=utf-8? Project ToolsVersion=4.0 DefaultTargets=Build xmlns=http://schemas.microsoft.com/developer/msbuild/2003; PropertyGroup *Configuration Condition= '$(Configuration)' == '' Debug/Configuration Platform Condition= '$(Platform)' == '' x86/Platform * This doesn't seem to be happening for a wixproj I have. I've added two new build configurations, and it keeps building one of those by default, called Debug SU. I want it to build Debug by default. I'm calling MSBuild from a script. Does anyone know how to have a specific configuration used by default when one isn't specified to MSBuild? I could add logic to check for this one solution and pass in a specific configuration, but that's a bit ugly if there is supposed to be a settable default. Thanks, - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/In-wixproj-default-Build-Configuration-ignored-or-not-settable-tp7565859.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
