Inside Microsoft® Visual Studio® .NET 2003 [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Inside Microsoft® Visual Studio® .NET 2003 [Electronic resources] - نسخه متنی

Brian Johnson

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید










Building Projects and Solutions


Once the projects, custom build configurations, and references are set in a solution, you can begin to work out the build scenarios that you want to run with the different configurations. To specify which projects in the solution should be built, you can use the Configuration Manager dialog box (shown in Figure 2-16). You can easily exclude projects that might give you problems, or you can simply save some time when you want to concentrate on a specific build in a solution.


Figure 2-16. Determining which project to build for a given build configuration



There's one more powerful build dialog box you can use to batch-build multiple-build configurations in a single go. The Batch Build dialog box (Project.BatchBuild), shown in Figure 2-17, isn't available for every solution type, but you can use it if your project consists of non-Web applications.


Figure 2-17. The Batch Build dialog box



The Batch Build dialog box lets you perform a number of important actions, including building, rebuilding, and cleaning your projects. Clicking the Build button initiates an incremental build for projects that are configured for such a build. The Rebuild button initiates a Rebuild All for all of the selected projects. Clicking the Clean button deletes the files that are output by a build so you can start clean or share your projects without unnecessary bulk. Note that in Visual Studio .NET the Clean command doesn't actually do anything for Visual Basic .NET and Visual C# projects. The Visual Basic .NET and Visual C# teams decided that this kind of functionality wasn't really necessary for managed projects, so it was left out.


/ 118