You are mixing server side and client side code.

If you want to spit out client side code on the server you can.

But best is to serialise your model data into JSON and put it on the client.

Rough example:

Update

@{ var uploadSettingsProvider = UniversalContainer.Container.Resolve<IUploadSettingsProvider>(); var js = new JavaScriptSerializer(); } myJavascriptObject.Models = @js.Serialize(myModels); 

You are mixing server side and client side code.

If you want to spit out client side code on the server you can.

But best is to serialise your model data into JSON and put it on the client.

Rough example:

Update

@{ var js = new JavaScriptSerializer(); } myJavascriptObject.Models = @js.Serialize(myModels); 

You are mixing server side and client side code.

If you want to spit out client side code on the server you can.

But best is to serialise your model data into JSON and put it on the client.

You are mixing server side and client side code.

If you want to spit out client side code on the server you can.

But best is to serialise your model data into JSON and put it on the client.

Rough example:

Update

@{ var uploadSettingsProvider = UniversalContainer.Container.Resolve<IUploadSettingsProvider>(); var js = new JavaScriptSerializer(); } myJavascriptObject.Models = @js.Serialize(myModels);