Home/ Questions/Q 8124269
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T06:24:47+00:00

I am using the TeamCity Visual Studio runner. I want to add a setting

  • 0

I am using the TeamCity Visual Studio runner. I want to add a setting that is not accessible from Visual Studio.

/Property:FileAlignment=4096

I typed that directly into the build step “Command line parameters.” The build log shows the error:

MSBuild command line parameters contains “/property:” or “/p:” parameters. Please use Build Parameters instead.

I don’t understand how to provide this to MSBuild from TeamCity and get rid of this warning!

1. Which kind of parameter should I use?

There are 3 kinds:

  • Configuration parameters
  • System properties
  • Environment variables.

I don’t want an environment or system variable because I don’t want this build to depend on anything external. I am going to try Config right now, but then I’m not sure I’m filling it in right.

2. How can I tell this parameter is actually getting used?

The build log, which seems only to have navigable/foldable xml-like levels with their program, did not say the build parameters.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This was solved. To clarify, Anthony told how to solve the problem in the commandline using MSBuild. It can also be solved on the commandline using devenv, per a ticket with Microsoft, the syntax is:

     devenv ..\..\mysolution.sln /Rebuild /Property:Config=Release;Platform=AnyCPU;Filealignment=512

    What I wanted, however, was to get Teamcity’s “Visual Studio Build” to accept the parameter. This was achieved as follows. In the box for Command line parameters, I entered: 

    /Property:FileAlignment=filealignment v:diag

    Then the output tab for Build Parameters shows:

    User Defined Parameters
Name                    Value passed to build
system.filealignment    512
system.verbosity        diagnostic
    • 0