ARM template deployment does not work when Parameter property is used

An unhandled exception of type ‘Microsoft.Rest.Azure.CloudException’ occurred in mscorlib.dll

Additional information: The request content was invalid and could not be deserialized: ‘Error converting value “http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#” to type ‘Microsoft.WindowsAzure.ResourceStack.Frontdoor.Data.Definitions.DeploymentParameterDefinition’. Path ‘properties.parameters.$schema’, line 291, position 100.’.

var deployment = new Deployment(); deployment.Properties = new DeploymentProperties { Mode = DeploymentMode.Incremental, Template = templateFileContent, Parameters = parameterFileContent };

File contents are being read as follows: JObject parameterFileContent = GetJsonFileContents(pathToParameter); public static JObject GetJsonFileContents(string pathToJson) { JObject templatefileContent = new JObject(); using (StreamReader file = File.OpenText(pathToJson)) { using (JsonTextReader reader = new JsonTextReader(file)) { templatefileContent = (JObject)JToken.ReadFrom(reader); return templatefileContent; } }

    }

[blumu]

OK, so that was it. The new Nuget (named Microsoft.Azure.Management.ResourceManager) introduces a breaking change: you now need to specify the entire template parameter file content including the $schema and contentVersion field, as opposed to just the "paramters" : { } node like in previous version of the nuget (Microsoft.Azure.Management.Resources).

[blumu]

@TianoMS I’m guessing you are referring to nuget Microsoft.Azure.Management.ResourceManager which I am also guessing is now replacing Microsoft.Azure.Management.Resources? I actually tried the latest version of this package (1.3.1) and got a weird error:

One or more errors occurred.The request content was invalid and could not be deserialized: 'Error converting value "{
 "myTemplateParameter": {
    "value": "ed103462dsfasdf"
 }
 }" to type 'System.Collections.Generic.Dictionary`2[System.String,Microsoft.WindowsAzure.ResourceStack.Frontdoor.Data.Definitions.DeploymentParameterDefinition]'. Path 'properties.parameters', line 78, position 424.'.

Is the Azure REST API now expecting a different format for the Parameters field?