Shulou(Shulou.com)06/02 Report--

This article focuses on "how to solve ADO.NET script code errors", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to solve ADO.NET script code errors.

Developers who move from CTP to ADO.NET scripts need to update their JADO.NET script code. For example, the Sys.Services.Components.Profile component mentioned on the official website has now become Sys.Preview.Services.Components.Profile.

In the CTP version, you simply add a ScriptManager control to the page and the default CTP core functionality (Atlas.js) is added. However, some other scripts are optional, such as AtlasUIGlitz.js files. If you want to use them, you need to manually add them to the references of ScriptManager, or define them in XML-Script.

In the RTM version, in order to use the functionality in Value-add, you must add specific script references to the ScriptManager. The following example shows how to reference all the scripts defined in Value-add. Note: here, the order of registration is very important, it indicates a "dependency chain".

The types defined in the Value-add script are transferred from the Sys.* namespace in the CTP version to Sys.Preview.*. This ensures a clear difference in functionality. Developers who move from CTP to Value-add scripts need to update their JavaScript code. For example, the Sys.Services.Components.Profile component has now become Sys.Preview.Services.Components.Profile.

At this point, I believe you have a deeper understanding of "how to solve ADO.NET script code errors". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.