He has conducted more than 300 corporate trainings on Microsoft technologies in India, USA, Malaysia, Australia, New Zealand, Singapore, UAE, Philippines and Sri Lanka. He is a Microsoft Most Valuable Professional (MVP) - Developer Technologies (Azure DevOps), Microsoft Certified Trainer (MCT), Microsoft Certified Azure DevOps Engineer Expert, Professional Scrum Developer and Professional Scrum Master (II). He is an engineer from Pune University and has done his post-graduation from IIT, Madras.
MICROSOFT TEAM FOUNDATION SERVER 2010 SOFTWARE
He has an experience of over 33 years in team management, training, consulting, sales, production, software development and deployment. Subodh is a Trainer and consultant on Azure DevOps and Scrum. A very interesting case could be to spawn workitems say of the type tasks in response to event of creation of other type of workitem like a scenario and link the spawned workitems to the scenario like workitem. Another example can be of creating a installer for output of build once the build completion event fires.
By handling such events we will be able to automate the tasks related to management of the project. For example, we can subscribe to Checkin event where the subscribing webservice will set the status of associated workitems to a custom value. These activities can be treated as events and it is possible to write event handlers for many of these events. TFS is a hive of activities related to configuration management, source control, work item tracking, builds etc. Responding to events published by the Team Foundation Server (TFS) is one of the extensibility opportunities which may be used most extensively. Visual Studio Team System exposes number of opportunities to extend its features and functionality.
0 kommentar(er)
