ASP.NET

Script compression allows you to reduce the size of scripts sent to the client, but it doesn’t reduce the number of separate scripts an ASP.NET AJAX page may be using. Besides the framework scripts MicrosoftAjax.js (the core framework) and MicrosoftAjaxWebForms.js (for partial rendering), there may be additional script references specified in the ScriptManager. ASP.NET AJAX compatible controls and components on the page may each require additional scripts that are embedded in their respective assemblies, adding even further to the number of scripts the page requires. A page can easily require a dozen or more scripts, even if there are no script references declared.

 

 

With the exception of Label and a handful of other controls, all DotNetNuke Web controls are contained as compiled controls inside the DotNetNuke.UI.WebControls namespace. Therefore, a single Register tag can handle registering them for use. This Register tag must be added at the top of any .ascx control that needs to use the controls.

 

Excerpt from Professional ASP.NET 3.5: in C# and VB

By Scott Hanselman

If you start up Visual Studio 2008 and open the Books.xml, which is listing 10-1 from the code download for the book Professional ASP.NET 3.5: in C# and VB (Wrox, 2008, ISBN: 978-0-470-18757-9) file into the editor, you notice immediately that the Visual Studio editor provides syntax highlighting and formats the XML document as a nicely indented tree. If you start writing a new XML element anywhere, you don't have access to IntelliSense. Even though the http://example.books.com namespace is the default namespace, Visual Studio 2008 has no way to find the Books.xsd file (listing 10-3 from the code download for the book Professional ASP.NET 3.5: in C# and VB); it could be located anywhere. Remember that the namespace is not a URL. It's a URI — an identifier. Even if it were a URL it wouldn't be appropriate for the editor, or any program you write, to go out on the Web looking for a schema. You have to be explicit when associating XML Schema with instance documents.

Excerpt from Beginning ASP.NET 3.5: in C# and VB

Get Started with Microsoft Visual Web Developer 2008 and ASP.NET 3.5

By Imar Spaanjaars

Although you could theoretically write ASP.NET 3.5 Web applications with Notepad or another text editor alone, you really want to install a copy of Microsoft Visual Web Developer. VWD is developed specifically for building ASP.NET Web sites, and as such, hosts an enormous amount of tools that will help you in rapidly creating complex ASP.NET Web applications.

Visual Web Developer comes in two flavors: as a standalone and free version called Microsoft Visual Web Developer 2008 Express Edition, and as part of the larger development suite called Visual Studio 2008 which is also available in different editions, each with its own price tag. Although the Express Edition of VWD is free, it contains all the features and tools you need to create complex and feature-rich Web applications. Getting VWD is easy. You can just download it from the Microsoft site as discussed next.

Excerpt from Professional ASP.NET 3.5: in C# and VB

By Bill Evjen

Prior to Visual Studio 2008, the ASP.NET AJAX product used to be a separate installation that you were required to install on your machine and the Web server that you were working with. This release gained in popularity quite rapidly and is now a part of the Visual Studio 2008 offering. Not only is it a part of the Visual Studio 2008 IDE, the ASP.NET AJAX product is also baked into the .NET Framework 3.5. This means that to use ASP.NET AJAX, you don't need to install anything if you are working with ASP.NET 3.5.

Excerpt from Professional ASP.NET 3.5: in C# and VB

ASP.NET 3.5 Windows-Based Authentication

by Bill Evjen

This article looks at Windows-based ASP.NET authentication, one of several different types of authentication measures ASP.NET 3.5 provides to use within your applications. ASP.NET has several ways of performing Windows-based authentication and we'll look at all of them: Integrated Windows authentication, Basic authentication, and Digest authentication. You'll also see in this article that if you are running your ASP.NET 3.5 pages on IIS 7 and Windows Vista, some of the authentication options will be configured with slightly different steps than in IIS 5.0 and 6.0 on Windows Server 2003 or Windows XP.