ASP.NET
  Home arrow ASP.NET arrow Page 2 - How to Develop a One-Page Web Application
ASP Free Forums 
.NET  
ASP  
ASP Code  
ASP.NET  
ASP.NET Code  
BrainDump  
C#  
Code Examples  
Database  
Database Code  
IIS  
Microsoft Access  
MS SQL Server  
Visual Basic.NET  
Windows Scripting  
Windows Security  
XML  
ASP Web Hosting  
ASP.NET Web Hosting 
Mobile Linux 
App Generation ROI 
Windows Web Hosting
 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
ASP.NET

How to Develop a One-Page Web Application
By: Murach Publishing
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 12
    2006-06-01

    Table of Contents:
  • How to Develop a One-Page Web Application
  • How to work with the Visual Studio IDE
  • How to add folders and files to a web site
  • How to open or close an existing web site

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    How to Develop a One-Page Web Application - How to work with the Visual Studio IDE


    (Page 2 of 4 )

    When you start a new web site, ASP.NET provides the starting folders and files for the site, including two files for the first web form of the site. The file named Default.aspx contains the HTML and asp code that defines the form, and the file named Default.aspx.vb contains the Visual Basic code that determines how the form works. Then, Visual Studio displays the aspx file for the web form as shown in figure 2-2.

    If you’ve used Visual Studio for building Windows applications, you should already be familiar with the Toolbox, Solution Explorer, and Properties window, as well as the Standard toolbar. They work much the same for web applications as they do for Windows applications. The Solution Explorer, for example, shows the folders and files of the web site. In this example, the Solution Explorer shows one folder named App_Data, plus the two files for the default web form.

    To design a web form, you use the Web Forms Designer that’s in the center of this Integrated Development Environment (IDE). When you start a new web site, this Designer is displayed in Source view, which shows the starting HTML code for the first (or only) web form of the application. Normally, though, you’ll do most of the design in Design view, which you can switch to by clicking on the Design button at the bottom of the Designer window.

    If you have your environment settings set to Web Developer, you’ll notice that different toolbars are displayed depending on what view you’re working in. In Source view, the Standard and HTML Source Editing toolbars are displayed. In Design view, the Standard and Formatting toolbars are displayed. This is typical of the way the Visual Studio IDE works. By the way, to change the environment settings, you use the Tools->Import and Export Settings command.

    As you go through the various phases of building a web site, you may want to close, hide, or size the windows that are displayed. You’ll see some examples of this as you progress through this chapter, and this figure presents several techniques that you can use for working with the windows.

    After you’ve designed a web form, you’ll need to switch to the Code Editor, which replaces the Web Forms Designer in the center of the screen. Then, you can write the Visual Basic code in the code-behind file for the form. One way to switch to the Code Editor is to double-click on the code-behind file in the Solution Explorer. If, for example, you double-click on the file named Default.aspx.vb, you’ll switch to the Code Editor and the starting code for that file will be displayed. Later in this chapter, you’ll learn other ways to switch between the Web Forms Designer and the Code Editor.

    As you work with Visual Studio, you’ll see that it commonly provides several ways to do the same task. Some, of course, are more efficient than others, and we’ll try to show you the best techniques as you progress through this book. Often, though, how you work is a matter of personal preference, so we encourage you to review and experiment with the toolbar buttons, the buttons at the top of the Solution Explorer, the tabs at the top of the Web Forms Designer or Code Editor, the shortcut menus that you get by right-clicking on an object, and so on. 

    The starting screen for a new web site


    Figure 2-2.  How to work with the Visual Studio IDE

    How to work with views and windows

    1. To change the Web Forms Designer from one view to another, click on the Design or Source button.
    2. To close a window, click on the close button in the upper right corner. To redisplay it, select it from the View menu.
    3. To hide a window, click on its Auto Hide button. Then, the window is displayed as a tab at the side of the screen, and you can display it by moving the mouse pointer over the tab. To restore the window, display it and click on the Auto Hide button again.
    4. To size a window, place the mouse pointer over one of its boundaries and drag it.

    Description

    1. When you start a new web site, the primary window in the Visual Studio IDE is the Web Forms Designer window, or just Web Forms Designer. The three supporting windows are the Toolbox, the Solution Explorer, and the Properties window.
    2. You use the Web Forms Designer to design a web form. Later, to write the Visual Basic code for the form, you use the Code Editor as shown in figure 2-14.
    3. Visual Studio often provides several different ways to accomplish the same task. In this book, we’ll try to show you the techniques that work the best.

    More ASP.NET Articles
    More By Murach Publishing


       · This article is an excerpt from the book "Murach's ASP.NET 2.0 Web Programming with...
     

    Buy this book now. This article is excerpted from the book Murach's ASP.NET 2.0 Web Programming with VB2005, written by Doug Lowe (Murach, 2006; ISBN: 1890774324). Check it out today at your favorite bookstore. Buy this book now.

    ASP.NET ARTICLES

    - Developing a Mini ASP.NET AJAX Server Centri...
    - Disadvantages of the ASP.NET MVC Framework
    - Advantages of the ASP.NET MVC Approach
    - ASP.NET Web Forms Weaknesses
    - ASP.NET Web Forms Meets ASP.NET MVC
    - Source Code for Saving and Retrieving Data w...
    - Using GridView to Save and Retrieve Data wit...
    - Handling Dynamic Images in ASP.NET 3.5 AJAX ...
    - Retrieving Data with AJAX and the GridView C...
    - Playing with Images in ASP.NET 3.5 AJAX Appl...
    - Saving and Retrieving Data with AJAX
    - Enhancing PHP Via the ASP.NET AJAX Framework...
    - Enhancing PHP Programming with the ASP.NET A...
    - Classes and ASP.NET AJAX
    - Using ASP.NET AJAX

     
    Best Practices for Windows Vista Migration Presentation
    Dell and Microsoft recently held a series of face-to-face seminars entitled, &qu....

     
    Creating a Culture for Code Reuse
    If you oversee development teams you know that like it or not proprietary and ex....

     
    Keys to Web Application Acceleration: Advances in Delivery Systems
    Accelerate Web apps by up to 5x. Ensure significantly faster access to the Web a....

     
    Optimizing Application Monitoring
    Tired of finding out from your customers that you're offline? This white paper e....

     
    Solaris to Solaris Migration -- Migrating applications from Sun SPARC to Dell PowerEdge R900
    This comprehensive Migration Guide reviews the approach that Principled Technolo....

     




    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 5 hosted by Hostway
    Stay green...Green IT