Creating Websites with Visual Studio

The preceding article Creating Websites with Visual Studio  gave you a quick overview of creating a website in VS. You simply chose New Web Site from the File menu, selected a language, selected the standard ASP.NET Web Forms Site template, and clicked OK. However, there’s more to the New Web Site dialog box than you saw in the previous article. You may have noticed that you can choose among a number of different templates that enable you to create different kinds of sites. But before looking at the different templates on which you can base your new website, you need to know a little more about the different project types that are available in VS.
Different Project Types.
In Visual Studio 2013 you can choose between two types of projects for creating ASP.NET Web Forms websites: Web Application Projects and Web Site Projects.
Web Application Projects Web Application Projects make it easier for developers who work in teams or who need more control over the contents of the site and their compilation and deployment processes to build websites with VS. The whole website is managed as a project, with a single project file that keeps track of all the content of the website. In VS, you create a new Web Application Project through the File ➪ New Project dialog box. The Web category contains a single template — ASP.NET Web Application — that lets you create a web application that can contain various ASP.NET-related technologies such as Web Forms, ASP.NET MVC, and Web API. This is part of Microsoft’s “One ASP.NET” initiative that aims to bring the various web technologies closer together in Visual Studio. For more information about these technologies, visit www.asp.net and click the Learn menu item.
Note:
For more information on One ASP.NET, and to learn more advancedtechniques, consult Professional ASP.NET 4.5 (Wrox; ISBN: 978-1-118-31182-0).
Web Site Projects Web Site Projects represent a project in VS for a website. You create a new Web Site Project by choosing File ➪ New Web Site or File ➪ New ➪ Web Site from Visual Studio’s main menu.

A Web Site Project site is simply a Windows folder with a bunch of files and subfolders in it. There is no collective file (known as the project file with a .vbproj or .csproj extension) that keeps track of all the individual files in the website. You just point VS to a folder, and it instantly opens it as a website. This makes it very easy to create copies of the site, move them, and share them with others, because no dependencies exist with files on your local system. Because of the lack of a central project file, Web Site Projects are usually simply referred to as websites, which is the term I use in the remainder of this articles.
Note You can’t use a Web Site Project to create MVC or Web AP applications.
-------------------------------------------------------------------------------------
Choosing between Web Site Projects and Web Application Projects

Customizing Toolbars in vs

          I n today tutorial we will Customizing Toolbars in vs and You can customize toolbars in three ways: you can show or hide the built-in toolbars, you can add and remove buttons on existing toolbars, and you can create your own toolbars with buttons you often use.Enabling and Disabling Toolbars

Enabling and Disabling Toolbars

                  You disable and enable existing toolbars by right-clicking any existing toolbar or the menu bar and then selecting the appropriate item from the list. Once the toolbar is displayed, you can use its drag grip at its left to drag it to a new location within the Toolbar area.

Editing Existing Toolbars

                  If you feel that an existing toolbar is missing an important button or that it contains buttons you rarely use, you can customize the buttons on the toolbar. To do this, right-cliack any toolbar or the menu bar, choose Customize, switch to the Commands tab, and select the toolbar you want to modify from the Toolbar drop-down. With the command buttons at the right, you can add new and remove existing commands, or change their order.

Creating Your Own Toolbars

              Creating your own toolbar is useful if you want to group some functions that you frequently use. To create a new toolbar, open the Customize window as explained in the preceding section. Click the New button and type a name for the toolbar. Then switch to the Commands tab and modify your toolbar as you would do with existing toolbars.

 

in simple words or steps:

You can change the layout, position, and content of toolbars in the integrated development environment (IDE). You can also add buttons to toolbars and change the assigned icon for any button.

1.     Create new toolbars

2.     To create a new toolbar

3.     On the Tools menu, choose Customize.

4.     In the Customize dialog box, select the Toolbars tab.

5.     Choose New.

6.     In the New Toolbar dialog box, type a name for the toolbar.

7.     Choose OK.

To add a command button to a toolbar

1.     On the Toolsmenu, choose Customize.

2.     In the Customize dialog box, select the Commands tab.

3.     Click Rearrange Commands.

4.     Under Choose a menu or toolbar to rearrange, select Toolbar and then choose the correct toolbar from the drop-down list.

5.     Click Add.

6.     In the Add Command dialog box, select category name from the Categories list and then choose an appropriate command from the Commands list.

7.     Click OK.

8.     Click Close and then click Close again.

To group commands on a toolbar

1.     On the Toolsmenu, choose Customize.

2.     In the Customize dialog box, select the Commands tab.

3.     Click Rearrange Commands.

4.     Under Choose a menu or toolbar to rearrange, select Toolbar and then choose the correct toolbar from the drop-down list.

5.     Select the command you want to begin a visual group.

6.     Click the Modify Selection drop-down list and select Begin a Group.

7.     A separator bar appears on the list of commands, above the selected command.

8.     Click OK, then click Close, and then click Close again.

9.     The command appears on the toolbar with a separator before it.

10.   Customize toolbar button images

11.   The IDE provides forty-two button images that can be exchanged with the default toolbar icons.

12.   To change toolbar button images

13.   On the Tools menu, choose Customize.

14.   In the Customize dialog box, select the Commands tab.

15.   Click Rearrange Commands.

16.   Under Choose a menu or toolbar to rearrange, select Toolbar and then choose the correct toolbar from the drop-down list.

17.   Select the toolbar command of which you intend to change the image.

18.   Choose Modify Selection.

Choose Change Button Image and select an alternative on the cascading menu.

 

Customizing Keyboard Shortcuts in vs 2013

Customizing the Document Window in vs

                 In today tutorial we will cover Customizing the Document Window in vs

  and the  Visual Studio gives you great flexibility with regard to how text is displayed in the Document Window. You can change things like font size, font color, and even the background color of the text. You can access the Font and Colors settings by choosing Tools ➪ Options, and then choosing Environment ➪ Fonts and Colors. Alternatively, press Ctrl+Q to put the focus on the Quick Launch textbox at the very top of the IDE. Then type font and press Enter to select the highlighted item Environment — Fonts and Colors. Quick Launch is a great tool for accessing features such as options and menu commands. For more information about Quick Launch, check out: http://bit .ly/1eljcko.

                        

  One thing I like to customize in the Document Window is the tab size, which controls the number of spaces that are inserted when indenting code. To change the tab size, choose Tools ➪ Options, and then under Text Editor choose All Languages ➪ Tabs. I usually set the Tab and Indent Size to 2 spaces, leaving the other settings in the Tab panel untouched. Another thing I like to customize is the number of line breaks before and after HTML elements. The Options window gives you full control over this: Select Text Editor ➪ HTML (Web Forms) ➪ Formatting and then click Tag Specific Options. In the list on the left you can select a tag and then with the settings on the right you can control how the tag is formatted. The Preview box makes it easy to see how the various settings change the formatting. Note that Web Forms has its own category in the Options dialog because it uses a different HTML editor under the hood than the other HTML-based editors found in Visual Studio.

    If you prefer to see line numbers in the gutter of the Document Window, choose Tools ➪ Options ➪ Text Editor ➪ All Languages and select the Line Numbers checkbox. With the exception of the Tab Size being set to 2 and the number of line breaks around a few HTML elements, all screen shots in this book show the default setup of VSEW.

tips time:
          It was developed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology.

Customizing Toolbars in vs 20113

ASP.NET 4.5.1 server

An Introduction to ASP .NET 4.5.1 server

 ASP .NET 4.5.1 server is describe here When you type a URL like www.wrox.com in your web browser and press Enter, the browser sends a request to the web server at that address. This is done through HTTP, the HyperText Transfer Protocol. HTTP is the protocol by which web browsers and web servers communicate. When you request the URL, you send a request to the server. When the server is active and the request is valid, the server accepts the request, processes it, and then sends the response back to the client browser. The relationship between the request and response is shown in Figure 1-8. Because you are using IIS Express, the server and the client are really the same machine. However, in a real-world scenario, you’ll host your website on an external web server where it can be accessed by many different clients.For simple, static files, like HTML files or images, the web server 

reads the file from its local hard drive and sends it to the browser. However, for dynamic files, such as ASPX pages, this is obviously not good enough. If the web server were to send the ASPX file directly to the browser as a text file, you wouldn’t have seen the current date and time in the browser, but instead you would have seen the actual code (<%: DateTime .Now.ToString() %>). So, instead of sending the file directly, the web server hands over the request to another piece of software that is able to process the page. This is done with a concept called Application Mapping or Handler Mapping, where an extension of a file (.aspx in this example) is mapped to an application that is capable of handling it. In the case of an .aspx page, the request is eventually handled and processed by the ASP.NET run time, part of the Microsoft .NET Framework designed specifically to handle web requests.

During the processing of the page, three main areas can influence the way the page eventually ends up in the browser:

➤➤ Static text. Any static text, like HTML, CSS, or JavaScript code you place in a page, is sent to the browser directly. You learn more about HTML, CSS, and JavaScript (a programming language used at the client) in this and subsequent chapters, including Chapter 3, which gives you a detailed look at CSS.

➤➤ ASP.NET Server Controls. These controls are placed in your ASPX page and when they are processed, they emit HTML that is inserted in the page.

➤➤ Programming code. You can embed code, like Visual Basic .NET or C#, directly in a page, as you saw in the previous Try It Out. In addition, you can place code in a separate code file. The official term for this code file is Code Beside. However, most developers refer to this as the Code Behind file, which is the term I’ll stick to in this book. This code can be executed by the run time automatically, or based on a user’s action. Either way, execution of the code can greatly influence the way the page is displayed, by accessing databases, performing calculations, hiding or showing specific controls, and much more. You learn more about this Code Behind file in the next chapter, and programming, Once the page is done processing, and all the HTML for the page has been collected, the HTML is sent back to the browser. The browser then reads it, parses it, and, finally, displays the page for you to look at. Because HTML is so critical for displaying web pages, the next section gives you an overview of HTML.

NEXT:Understanding HTML more