Scrigroup - Documente si articole

Username / Parola inexistente      

Home Documente Upload Resurse Alte limbi doc  

AccessAdobe photoshopAlgoritmiAutocadBaze de dateCC sharp
CalculatoareCorel drawDot netExcelFox proFrontpageHardware
HtmlInternetJavaLinuxMatlabMs dosPascal
PhpPower pointRetele calculatoareSqlTutorialsWebdesignWindows
WordXml

AspAutocadCDot netExcelFox proHtmlJava
LinuxMathcadPhotoshopPhpSqlVisual studioWindowsXml

Build

Visual studio

+ Font mai mare | - Font mai mic




DOCUMENTE SIMILARE

Trimite pe Messenger
AVIcode
Tools for Testers
Architecture
Introduction: Understanding Application Life-Cycle Pain Points
Compuware
Tools for Developers
Microsoft Visual Studio 2005 Team System
Visual Studio 2005 Team Foundation Server
Managing the Ongoing Project
Customizing Visual Studio 2005 Team System Using Process Templates


Build

We’ve built our application as a developer, now it’s time to share it out to the rest of our team.

Visual Studio has always done a good job of building applications on your desktop, but it falls short in a team environment.




Visual Studio Team System provides build automation that is essentially a ‘build lab in a box’. With this build automation, we can do the following with little or no extra overhead:

  • Capture what files, work items, test results, code coverage, etc are include for a given build and be able to answer questions like: “Is today’s build better than yesterday’s?”
  • Create a snap shot of everything – source code files, libraries, compilers, etc – that was used to create a given build, so you can reproduce it
  • Provide a way to schedule builds to run on a fixed schedule

All of this is done by tightly integrating with Visual Studio Team System; let’s use an example build configuration to build our application and share it with our team.

Once our build finishes, our test team will know immediately when there is a good build to pick up and start testing.

In Team Explorer, select the Team Builds node, right-click and choose New Team Build Type

In the resulting wizard, name the build type AdventureWorksNightlyBuild and click Next

Click on the (Select All) check box and click Next



Under Configuration choose Debug from the drop down box and click Next



Specify tfsrtm as the build machine name, C:nightlybuilds for the Build Directory and tfsrtmnightlybuilds for the Drop Location





Don’t enable tests and code analysis for now, just click Next (You can see we can associate other activities into build such as testing, and code analysis!)

Click Finish to finish the wizard

In Team Explorer, start the build by right clicking the AdventureWorksNightlyBuild under Team Builds in the Team Explorer, and selecting Build Team_Project AdventureWorks…

Click on the Build button to commence the build

As the build is running, you will see the current progress. When finished, expand each section to summarize the results.

Open the Associated Work Items and view the work items that were associated with this build (Now we can see why we need to ensure all work is associated with work items – not only to help tracking, but it also allows us to fully integrate into the build cycle)



Close all document windows (Window, Close All Documents)






Politica de confidentialitate



DISTRIBUIE DOCUMENTUL

Comentarii


Vizualizari: 681
Importanta: rank

Comenteaza documentul:

Te rugam sa te autentifici sau sa iti faci cont pentru a putea comenta

Creaza cont nou

Termeni si conditii de utilizare | Contact
© SCRIGROUP 2021 . All rights reserved

Distribuie URL

Adauga cod HTML in site