typical developer day

@Typical developer day

Ricci Gian Mariahttp://blogs.ugidotnet.org/rgmhttp://www.codewrecks.comalkampfer@nablasoft.com

@alkampfer…

@• The new team explorer and IDE• Plan and activate your task • How to manage interruptions of work• Code Review / Gather feedback• Cure the health of the build• Use branching to do complex-work• Intellitrace to the max in production environments• Preemptive integration with TFS• Extend your VS.

Agenda

@New Team explorer

Task based • My Work• Pending Changes• Work Items• ...

Make developers concentrate on «what to do»More coincise and «browse-like» useMore functionality (Es. search WI)

@New First Level menu of Team ExplorerVisualize the task that are associated to the user• In progress work• Suspended Work• Available Work Items• Code Reviews

My Work

@Each ALM process has the concept of “planning”Usually planning phase is used to

Decide user story for the next iterationDecompose user stories in taskAssign tasks to people or resource type

Planning is a vital part of a developers life, to avoid “what should I do next” syndrome

An intro to planning

@It is the easiest way to visualize a list of task available to current userIs a simple shortcut to a series of default queryYou can personalize a query and save into My Query to change the logic behindIs the starting point of your work

Available Work Items

@Summarize the “stuff” you are working with

Work Items activeSource Control Pending changes.

Inform the team on “who is working with”Supports the concept of “suspension of work”

Mitigate “context switch”Manage interruptions

In Progress Work

@Caused usually by “more priority task to do in the middle of the current task”

Hotfix bug in productionHotfix bug in dev because the team is blockedBroken buildChange of priority

This is usually associated to a cost for “context switching”Welcome “suspend work” in VS2012

Interruption of works

@Ask for work review by other member of the team

Not familiar with the project / areaCode is complex ex. Heavy multithreadingUnsure of something

Feedback by the usersNew feedback tool Integrated in TFS

Code review and feedback

@A single line of code is dangerousBranch can save your time

Branch for production codeBranch for long and complex feature to add

Avoid “fear of the merge”

Use Branch to organize code lines

@Use Branch to organize code lines

HOTFIX

Secu

rity

BugFixe

d

PRODUCTION

TEST - QASta

ble

REL 1HOTFIX

DEV

SP1

@Known as historical debugger Introduced in VS2010With VS2012 is available to use in production

PowerShell based integrationSimple to use by IT teamSeamless start-stop trace on production server

Intellitrace ™

@Instrument assembly to automatically send “incident” on exceptionIntegrated on TFS-Visual Studio

Incident collector provide the bridge with TFSGenerates Work Items on incidentDedicated section of Team Explorer

Greatly reduced time-to-supportMakes user happier

Preemptive integration

@In VS2012 macro support was removedYou can automate everyday task with plugins

Install VS2012 sdkCreate a new plugin project

SuggestionsUse VS2010 macro recorder to understand API to useTry the SDK samples (http://tinyurl.com/VSSDKSamples)

MSDN: http://tinyurl.com/VSSDKMsdn

Extend VS with plugin

Grazie agli sponsor