Getting started with ASP.NET AJAX in Visual Web Developer
2006-11-28 22:20
603 查看
Getting started with ASP.NET AJAX in Visual Web Developer
Once you download ASP.NET AJAX, you are ready to start using Visual Web Developer and Visual Studio 2005 for your development.
The first thing you will notice when you open up Visual Web Developer is that you now have a new project type called ASP.NET AJAX Enabled Web Site as seen below.
Selecting this option will give you a web site with a different default.aspx and web.config than a regular ASP.NET web site. You'll also have the ASP.NET AJAX Extensions pre-populated in your toolbox for easy drag and drop into the designer.
Tip: If you are going to be creating a lot of ASP.NET AJAX pages or are going to be adding ASP.NET AJAX extensions to your existing web site, you may want to create item templates out of your default.aspx and web.config files. In order to do this, you will use the Export Template wizard on the File menu. Choose Item Template in the wizard, select references as well as a default name and description for your templates and you are ready to use them over and over again.
Once you export your templates using the wizard, you will be able to see them in the Add New Item dialog as shown below.
Give Visual Web Developer a run for creating your ASP.NET AJAX web site and let us know your feedback.
Couple of gotchas that we've heard about to date:
1. One issue that people have been running into is with markup intellisense and source code preservation inside of the new controls like ScriptManager, UpdatePanel, etc. in HTML source view. This is a known bug that will be fixed in Visual Studio SP1 and there's also a workaround that exists currently. See this post for more details regarding this issue and how you can work around it.
2. Another fairly common gotcha is to forget to change <compilation debug="true"> to <compilation debug="false"> in your web.config when you are ready to deploy your application. The default web.config template has debug="false" but upon F5, Visual Studio will automatically change this to debug="true" to enable you to debug your app. If you deploy your application without changing this back to debug="false", you are paying via both a higher payload as well as slightly degraded runtime performance.
Thanks,
-- Bash
Published Wednesday, November 22, 2006 10:43 PM by WebDevTools
Once you download ASP.NET AJAX, you are ready to start using Visual Web Developer and Visual Studio 2005 for your development.
The first thing you will notice when you open up Visual Web Developer is that you now have a new project type called ASP.NET AJAX Enabled Web Site as seen below.
Selecting this option will give you a web site with a different default.aspx and web.config than a regular ASP.NET web site. You'll also have the ASP.NET AJAX Extensions pre-populated in your toolbox for easy drag and drop into the designer.
Tip: If you are going to be creating a lot of ASP.NET AJAX pages or are going to be adding ASP.NET AJAX extensions to your existing web site, you may want to create item templates out of your default.aspx and web.config files. In order to do this, you will use the Export Template wizard on the File menu. Choose Item Template in the wizard, select references as well as a default name and description for your templates and you are ready to use them over and over again.
Once you export your templates using the wizard, you will be able to see them in the Add New Item dialog as shown below.
Give Visual Web Developer a run for creating your ASP.NET AJAX web site and let us know your feedback.
Couple of gotchas that we've heard about to date:
1. One issue that people have been running into is with markup intellisense and source code preservation inside of the new controls like ScriptManager, UpdatePanel, etc. in HTML source view. This is a known bug that will be fixed in Visual Studio SP1 and there's also a workaround that exists currently. See this post for more details regarding this issue and how you can work around it.
2. Another fairly common gotcha is to forget to change <compilation debug="true"> to <compilation debug="false"> in your web.config when you are ready to deploy your application. The default web.config template has debug="false" but upon F5, Visual Studio will automatically change this to debug="true" to enable you to debug your app. If you deploy your application without changing this back to debug="false", you are paying via both a higher payload as well as slightly degraded runtime performance.
Thanks,
-- Bash
Published Wednesday, November 22, 2006 10:43 PM by WebDevTools
相关文章推荐
- [转]Getting started with ASP.NET Web API OData in 3 simple steps
- Beginning DotNetNuke 4.0 Website Creation in VB 2005 with Visual Web Developer 2005 Express: From No
- [转载]Getting Started with ASP.NET vNext and Visual Studio 14
- Getting started with ASP.NET Core MVC and Visual Studio
- Displaying Data in a Chart with ASP.NET Web Pages (Razor)
- Designing with WebParts in Visual Web Developer
- Performing Data Access->Working with Databases in Visual Web Developer 2005 Express Edition
- Getting Started with ASP.NET MVC
- 解决用Visual Web Developer 2005编译asp.net 2.0项目时无dll文件的问题
- Building a Web 2.0 Portal with asp.net ajax 第一章
- http://www.asp.net/mvc/overview/getting-started/getting-started-with-ef-using-mvc/creating-an-entity-framework-data-model-for-an-asp-net-mvc-application
- 使用Visual Web Developer 2008 Express 创建Asp.Net网站
- Create an ASP.NET Core web app in Visual Studio Code
- asp.net visual web developer 第一天
- [转]Getting Started with ASP.NET Web API 2 (C#)
- Web Servers in Visual Studio for ASP.NET Web Projects
- Getting Started with NHibernate and ASP.NET MVC- CRUD Operations
- Replace JSON.NET with ServiceStack.Text in ASP.NET Web API
- Getting Started with Rational XDE Professional: A Guide for Visual Studio .NET Developers
- Getting Started With LINQ in Visual Basic (翻译 + 评论)