ASP.NET Ajax client-side framework failed to load

I am getting error message "ASP.NET Ajax client-side framework failed to load."  During the compile I see the warning messages:

Warning    1    The primary reference "Microsoft.ScriptManager.MSAjax, Version=4.5.6.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" could not be resolved because it was built against the ".NETFramework,Version=v4.5" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v4.0".  

Warning    2    The primary reference "Microsoft.ScriptManager.WebForms, Version=4.5.6.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" could not be resolved because it was built against the ".NETFramework,Version=v4.5" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v4.0".  

Warning    3    The primary reference "Microsoft.AspNet.Membership.OpenAuth, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" could not be resolved because it was built against the ".NETFramework,Version=v4.5" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v4.0".  

The targeted Framework is 4.0 because it has to be.

This application is a test application to explore a process.  The only thing I care about on the Default page is the code behind and a JQuery document.ready event which calls a function with a JQuery get for another page whereby the process takes place.  I do need to be sure that the function with the "get" will work on a page that uses a master page.

So I need to know how to change the Script manager in the master page to be that used in the 4.0 framework.  I am not using anything dealing with membership.OpenAuth so I don't care about that warning.
Edward JoellAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Carl TawnSystems and Integration DeveloperCommented:
If you are using JQuery, rather than Microsoft AJAX, then you shouldn't need a ScriptManager on your page at all. Have you tried removing it and just using a standard reference to the JQuery library?
Edward JoellAuthor Commented:
The script manager was on the master page not my page and it seemed to be running a bunch of scripts there.

However, I devised a very simple method to resolve this.  I deleted the site.master from the project then I did an add for a Site.Master from a VS 2010 project.  Then I created a new folder under the root called "Styles" and added an existing site.css from the same vS 2010 project.  Now all is right with the world.  The sun is shining, the birds are singing, and I am happy, and can get on with the real development issues with which I am dealing.  Thanks to everyone who took a look at this.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Edward JoellAuthor Commented:
I found an excellent work-around so that I did not have to deal with the issue at all.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP.NET

From novice to tech pro — start learning today.