Home/ Questions/Q 6049911
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T07:37:47+00:00

I am attempting to find a place to start debugging this issue at. I

  • 0

I am attempting to find a place to start debugging this issue at.
I do not experience this issue if I create a new, MVC2 project, but I am trying to integrate into our companies existing MVC solution.

I am adding a ScriptManager to the MasterPage. Something like this:

<telerik:RadScriptManager ID="ScriptManager1" runat="server" EnableTheming="True" EnablePageMethods="True">
</telerik:RadScriptManager>

Here is what I see when I try and run.

I’m extremely new to MVC and unsure of where/how to start debugging this. I have a hunch it has something to do with either the Global ASAX or Web Config file, but without any more information I’m not sure where to begin poking around.

Has anyone seen this before?

partial-answer: it seems that moving the script manager inside of the closing tag resolved this issue, but the second I tried to add a control to my View I am back to looking at garbage. Plus, it doesn’t match what I had to do in the default app. Wondering why.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Some asp.net controls simply won’t work in MVC because they rely on features that MVC doesn’t support, such as viewstate. I’m not sure if the Telerik ajax controls are in this boat or not, but you can’t assume any control will work. Generally, the more complex the control, the less likely it will work.

    I notice that you have it working in a default project, but perhaps that project has no real data or doesn’t use the same features that your production app uses.

    • 0