How to build a site quickly with Dreamweaver

Building a site in Dreamweaver is the second key step in the development of a Web site. Here the establishment of the site, in fact, is in the Dreamweaver to define the site, planning site structure, deployment development environment. Define the site is to better use the "file" panel to manage the site files, but also to reduce the occurrence of some errors, such as path error, link error and so on. Many beginners start to do the Web page, only know to do a single Web page, the document of the Organization, the structure does not manage, did not classify the file management, so that the entire site structure appears very messy; So before the development should carefully plan the site structure. Since this book is about the development of the ASP.net network application, it should deploy the Dreamweaver about the development run component before it is developed.

Effect description

Figure 2-1 shows the site "Dreamweaver100" built with Dreamweaver, which is the 75th to 90th example of the site where the toy company built the site. This example is to introduce the establishment of this site method.

Creative Thinking

Open the Dreamweaver MX 2004 software and perform the site | Site Administration command, in the Pop-up Site Administration dialog box, select New, and then follow the steps of the new site to set up and save the production.

Operation Steps

Step one defines the site

(1) Start the new site. Start Dreamweaver MX 2004, switch to the Files panel, click Manage Sites, and then click the New button in the Manage Sites dialog box, as shown in Figure 2-2.

　　

(2) Set the Site property parameters. In the pop-up Dreamweaver 100 Site Definition dialog box, define the site in edit file, edit file, 2nd part, edit file, 3rd part, as shown in Figure 2-3.

Tip: This example is to switch to the "Basic" tab to set up the site, we recommend that beginners to set up the site in this way, and then through the "Advanced" tab to the site for more detailed settings.

Step 4 in Figure 2-3 If you choose No, I do not want to use server technology, then the site is a static web site, and step 6 is executed directly. Static site and dynamic site is not the difference between the Web site has no GIF, Flash animation, but refers to there is no interaction. "Interactive" refers to the site according to the user's requirements and choices can be dynamically changed and response, can automatically update the Web site, automatic generation of bulk pages, according to the user's conditions (time, browser type, user access to the site, etc.), automatically generate different pages.

Step 5 in Figure 2-3 is primarily based on a familiar server technology. If the reader is familiar with ASP server technology, you can choose "ASP JavaScript", "ASP VBScript" one of the two scripts, if you are familiar with ASP.net, you should choose "ASP.net C #", "asp.net VB" or "ASP." NET Jscript.

Step 7 in Figure 2-3 if you select Edit locally, then upload to the remote test server, then after step 9, you will go to the test file for the remote server settings, if you choose to "use the local network directly on the remote test server for editing," then in the 8th You should enter the address of the server in a step operation, and for security reasons, it is recommended that beginners do not edit the Web site in this way.

Step 8 in Figure 2-3 enters the physical storage location of the Web site on the local network, and its settings are generally consistent with the physical storage location of the default site home directory for the IIS server.

　　

(3) then test the site and complete the site definition, as shown in Figure 2-4.

Tip: The 1th step shown in Figure 2-4 enters "http://localhost/" instead of the physical path set in the 8th step of Figure 2-3, and now opens IE to access all asp.net pages under the http://localhost site.

Step 5 in Figure 2-4 is about whether to upload the settings to the remote server after each page is edited, and if you choose "Yes, I want to use remote server", after step 7, you will go to the test file for the remote server settings.

　　

Step Two planning site structure

Previously said, to carefully plan the structure, the site of the file classification management, the different types of documents are placed under different directories. The site structure of this example is planned as follows: Site Directory planning for all Web page files, folder "Bin" for the deployment of DreamweaverCtrls.dll control, folder "Dat" for the database, folder "Images" for storing site-related picture files. The specific actions are as follows:

Create a new folder "Bin", "Images", and "Dat" for the site "Dreamweaver100" in the file panel, as shown in Figure 2-5.

Tip: Not every new site must include these three folders. However, the folder "Bin" is generally used to store the necessary components of the operation of the site, the folder "Images" is generally used for storing site-related picture files. When the site planning, the reader can plan a little more, such as the site's image in a file, the product image in another file and so on. Note, however, that if you plan the folder name of the necessary component to hold the site running, you should correspond to the folder used in step three (2)

　　

Step three Deploy site components

(1) Select the "File" | "new" menu command and create a dynamic page as "asp.net VB" in the Pop-up new Document dialog box, as shown in Figure 2-6.

Hint: Because this book mainly explains the development of ASP.net network application, it is to develop through new asp.net dynamic page. And you can't do the next step without creating a new, blank asp.net dynamic page.

　　

(2) Set up the deployment directory. Switch to the Applications panel, select the Bindings tab, click the Deploy button, and set the deployment directory to "C:inetpubwwwrootbin" in the "Deploy supporting files to test Server" dialog box, as shown in Figure 2-7.

Hint: The binding here is actually the binding DreamweaverCtrls.dll file, DreamweaverCtrls.dll file is the necessary component to run ASP.net server behavior under Dreamweaver. The DreamweaverCtrls.dll file name and its directory bin name cannot be changed, and the bin folder must be saved in the root directory of the site.

The 75th to 90th example of this book will be developed for Web applications at this site.

　　

(3) If the "aspnet_client" file is not found under the "C:intepubwwwroot" folder, copy the CD-ROM source instance 2aspnet_client folder to the C:intepubwwwroot folder.

Tip: When you install the. NET Framework, the "aspnet_client" file is installed by default under the "C:intepubwwwroot" folder (System disk is C).

Build a good development environment, in the Dreamweaver after the establishment of a good site, can be said to be the network application of the processing plant completed, you can process a variety of products-Web pages, Web applications and so on.

Building a site in Dreamweaver is the second key step in the development of a Web site. Here the establishment of the site, in fact, is in the Dreamweaver to define the site, planning site structure, deployment development environment. Define the site is to better use the "file" panel to manage the site files, but also to reduce the occurrence of some errors, such as path error, link error and so on. Many beginners start to do the Web page, only know to do a single Web page, the document of the Organization, the structure does not manage, did not classify the file management, so that the entire site structure appears very messy; So before the development should carefully plan the site structure. Since this book is about the development of the ASP.net network application, it should deploy the Dreamweaver about the development run component before it is developed.

Effect description

Figure 2-1 shows the site "Dreamweaver100" built with Dreamweaver, which is the 75th to 90th example of the site where the toy company built the site. This example is to introduce the establishment of this site method.

Creative Thinking

Open the Dreamweaver MX 2004 software and perform the site | Site Administration command, select New in the Pop-up Site Administration dialog box, step through the new site steps, and finally save the production