لطفا منتظر باشید ...
• Table of Contents
• Index
Sams Teach Yourself Visual Studio® .NET 2003 in 21 Days
By
Jason Beres
Publisher
: Sams Publishing
Pub Date
: January 14, 2003
ISBN
: 0-672-32421-0
Pages
: 696
Sams Teach Yourself Visual Studio .NET in 21 Days will help developers that are new to application development and experienced developers understand how to use the .NET Framework and Visual Studio .NET to rapidly develop any type of computer application. The Visual Studio .NET development environment is the most comprehensive developer tool ever created, putting that together with the .NET Frameworks' Class Libraries, the developer has everything he or she needs to get up-to-speed on Microsoft's latest revolution in application development. This book will guide the developer through using the VS .NET IDE, the Visual Basic .NET and C# language, and the supporting tools available from Microsoft to create Windows and Web-based applications. The market is full of books that pretty much say the same thing, which is already available in the help files, the author of this book has written and deployed over a dozen successful applications using Visual Studio .NET and the .NET Framework. All of his expertise and experience is used to give you the most comprehensive title on using Visual Studio .NET.
Adding New Project Items or Projects
When working with projects in VSS, you're actually checking out only individual files, not the Visual Studio project file or the Visual Studio solution file. That means any time you add a new item to your projects or you rename an item in your project, you must check out the project file in the solution.Adding an item is a straightforward task. When you add an item, the project file must be updated with the information about the new file. Because a project file in Visual Studio tracks each item in a project, the VSS database must be notified of your changes. After the normal Add Item dialog pops up and you select the type of item you're adding and give it a name, the Check Out For Edit dialog for the project pops up, as Figure 20.16 demonstrates.
Figure 20.16. Checking out the project file when adding new items.
At this point, the new item is added and the project file is updated. The problem is that the project file must be checked back in to VSS or no one can check it out to get your new changes. Therefore, as soon as you can, you must check the project file back into VSS so that other developers can access it. Because the default for a new item is checked in, when someone else grabs the latest version of the project, he'll see your newly added file.If you add a new project to a solution, the solution file is checked out and you're prompted with a warning similar to Figure 20.17.
Figure 20.17. Warning dialog box when adding a new project to a solution.
Because both Visual Studio .NET and VSS maintain a hierarchy of the project and files in your solutions, the VSS database must associate a newly added project with the correct solution when adding a new project. That means you must create a new project folder underneath the existing root of the project in VSS. To get an idea of how this works logically, the Check In dialog shown in Figure 20.18 shows the hierarchy after adding a new project to a solution.
Figure 20.18. Solution hierarchy after adding a new project to a solution.
You can see that when VSS checks files back in, they're logically listed as File Below ProjectX or Items Below SolutionX. When you click the OK button on the Check In dialog after adding a new project to a solution, you're prompted to give the new project names in VSS. You can use the same project names that you use in the solution, and the correct hierarchy is maintained for others who attempt to access this solution.
