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

Editor to share with you how to quickly grasp the use of VS2003, I believe that most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!

If you have written a custom client-side JavaScript script in your web application and will use AJAX, please read on to learn how to avoid this common problem (note: if you want to see a list of other tips, tips and complicated posts I have posted, please visit this page here).

Symptoms:

You will see strange behavior when you add a new client-side JavaScript script to a previous project that successfully upgraded from VS 2003 to VS 2005. When using an ASP.NET AJAX UpdatePanel control, this strange behavior sometimes involves making a full-page postback on the page, not just incremental local updates. When you open your web.config file, you will see the elements, like this:

System.web > configuration >

Background:

Many server-side controls in ASP.NET 1.0 and 1.1 do not output XHTML-compatible identities. ASP.NET 2.0 has changed this, and by default, all server-side controls output XHTML-compliant logos (note: you can learn more about standards compatibility in ASP.NET 2.0 in this excellent MSDN article).

One of the things we noticed in the early ASP.NET 2.0 beta when using VS2003 was that when upgrading customer applications, many applications assumed that the page output was not compatible with XHTML. Change the default output of our server control to be compatible with XHTML, which sometimes modifies the visual display of the page. For backward compatibility, we have added the above setting to allow developers to set the control to display in Legacy mode (that is, like ASP.NET 1.1, it outputs a non-XHTML identity), or Transitional mode (XHTML Transitional), or Strict mode (XHTML Strict).

By default, when you use the Web Project Migration Wizard for upgrading from VS 2003 to VS 2005 (whether it's a website or a web application project), this legacy configuration will be added to your web.config file.

Microsoft employees are concerned about Visual Studio2003 code editing

A few minutes to let you know the match of Visual Studio Boost.

It strongly shows that the relevant skills of Visual Studio debugging are the same as those of

Download and install the annoying Visual Studio 2005 SP1

Visual Studio 2010 develops and deploys 64-bit programs

Solution:

Unless you know that there will be problems when your site is running in XHTML mode (but you haven't had time to correct it), I always suggest removing this section from your web.config file, or you can explicitly set it to Transitional or Strict.

This will make your HTML output up to standard, and it will also cause the HTML output of your server control to be well formed, that is, the start and end tags always match. This is especially important when you use AJAX technology to dynamically replace the contents of certain HTML elements on your page, otherwise client-side JavaScript scripts sometimes get confused about container elements, resulting in errors. It will also ensure that ASP.NET AJAX will work properly on your website.

The above is all the contents of the article "how to quickly grasp the use of VS2003". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

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.