Passing in an object to DeploymentProperties.Parameters fails to serialize and results in ARM deployment rejection

Creating an Azure Resource Manager Deployment by specifying the parameters as an object in the request results in the parameters being dropped from serialization:

deployment.Properties = new DeploymentProperties
{
    Mode = DeploymentMode.Incremental,
    TemplateLink = new TemplateLink("[redacted]"),
    Parameters = new
    {
        diskStorageAccountName = "value",
        imageVhdPath = "value",
        virtualNetworkName = "value",
        virtualNetworkSubnetName = "value",
        vmName = value,
        vmAdminUserName = "value",
        vmAdminPassword = "value"
    }
};

generates the following request:

PUT https://management.azure.com/subscriptions/[redacted]/resourcegroups/[redacted]/providers/Microsoft.Resources/deployments/gameserver?api-version=2014-04-01-preview HTTP/1.1
x-ms-client-request-id: [redacted]
accept-language: en-US
Authorization: [redacted]
User-Agent: Microsoft.Azure.Management.Resources.ResourceManagementClient/3.0.0.0
Content-Type: application/json; charset=utf-8
Host: management.azure.com
Content-Length: 200
Expect: 100-continue

{
  "properties": {
    "templateLink": {
      "uri": "[redacted]"
    },
    "parameters": {},
    "mode": "Incremental"
  }
}

which results in a 400 result in the status, as parameters are missing from the request.

[fabsenet]

this issue is over two years old and I still struggle with it today. I found no other sources on the web and I have no idea how others are doing this. There should be a .Net-way of providing parameters but there isn’t.

I created the working json parameters string from objects in this way to mirror the json parameters template file:

var parametersObject = new
{
    myParam1 = new { value = "abc" },
    myParam2 = new {value = "def" },
    command3 = new { value = "aaa" }
};

var parametersJson = JsonConvert.SerializeObject(new { parameters=parametersObject });

[adrianhall]

My apologies for this taking so long. Is this still an issue?