When specifying a platform to build in the Visual Studio builder tasks' configuration page the parameter is not passed to further steps correctly.
The parsing of arguments in bamboo is good, but devenv is a 'special' beast:
1. It has parameters pairs separated by whitespace
2. The platform to build uses the pipe symbol (what were they thinking?)
An example: devenv Project.sln /Rebuild "Release|Any CPU"
To get around the first issue we changed the options to: /Rebuild '"Release|Any CPU"'
To get around the second issue we needed to modify devenvrunner.bat to add quotes to the argument if it contained a pipe character.
I have attached our fix for the batch file.
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[BAM-9922] Visual Studio builder task does not allow the pipe symbol to be passed in the arguments
@Goldpitcher: I suggest using the MSBUILD task instead of the VStudio.
Here you can manually set the commandline parameters
We use for our x64 build the following Options
/t:Rebuild /m /p:Configuration=Release /p:Platform="x64"
and you don't have problem with the still broken x64 Visual Studio task
Bill Tutt
added a comment - Looking at the .net plugin source history it was fixed for version 3.9 of the .net plugin on 8/7/2012.
Bill Tutt
added a comment - Looking at the .net plugin source history it was fixed for version 3.9 of the .net plugin on 8/7/2012. 
Luke [Goldpitcher]
added a comment - Hi,
This is Luke from Korean partner, Goldpitcher.
One of our custoemr has the same issue but they said it is occurring only with 64 bit build under Bamboo 4.3.3 (dotnet plugins 3.5).
Is this issue is fixed in Bamboo 5.x version (dotnet plugin 5.0.1) ?
Please let me know.
Cheers,
Luke
Luke [Goldpitcher]
added a comment - Hi,
This is Luke from Korean partner, Goldpitcher.
One of our custoemr has the same issue but they said it is occurring only with 64 bit build under Bamboo 4.3.3 (dotnet plugins 3.5).
Is this issue is fixed in Bamboo 5.x version (dotnet plugin 5.0.1) ?
Please let me know.
Cheers,
Luke 
Brian Crosen
added a comment - The pipe was working just fine in version 3.4, but now it is broken again in version 3.5. There was a one line change to devenvrunner.bat in the 3.5 version.
Version 3.4 contains: echo "%~1" | findstr "|"
Version 3.5 contains: echo "%~1" | findstr /r /c:". ."
Brian Crosen
added a comment - The pipe was working just fine in version 3.4, but now it is broken again in version 3.5. There was a one line change to devenvrunner.bat in the 3.5 version.
Version 3.4 contains: echo "%~1" | findstr "|"
Version 3.5 contains: echo "%~1" | findstr /r /c:". ." not 100 % sure
but it seems like a problem with a "variable/value" substitution I played around with different numbers ob escape character '^',
I don't think this problem can be solved generically with batch files because cmd.exe is very choosy interpreting the parameters (so you probably MUST use quotation marks or MUST NOT and so on...
I suggest using something different like .vbs or similar to run the command.
as already mentioned I have a workaround by using a "script" task to call the command direct, without the devenvrunner.bat
Probably a good solution would be to "simplify" the batch file and do the whole parameter preparation in the JAVA part ?
Hi Norbert,
Thanks for verifying. Do you know what the problem specifically is with the devrunner.bat?
Thanks
James
2 days ago I updated to Bamboo 4.0 so yes Plugin 3.5 is installed
Atlassian Bamboo .NET Plugin 3.5
But I also looked into this topic, the problem lies within the "devrunner.bat"
Hi Norbert,
Can you confirm that the right version of the plugin, 3.5, is active by looking for the plugin in the Plugin Manager (accessible via the administration screen)?
If everything looks ok, ill schedule this to be looked at again.
Sorry for the hold up!
Thanks
James
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Bamboo Data Center, please check our public roadmap.
Kind regards,
Bamboo Data Center