Omaha ALM User Group Meeting (15 Jan 2013)
Happy New Year Omaha Team System User Group! 2013 is going to be an exciting year for our group. First, as many of you are aware, the Team System name has been retired for a couple of years, we have decided to change the name to** Omaha ALM User Group** in order for the group to reflect scope and direction of the group. ALM is about utilizing tools and automation to support the people and processes across the complete application lifecycle. In addition the name of the group is technology agnostic so we hope to have topics that cover other platforms and ALM toolsets. Here are some potential topics to get an idea of what we could cover: *Agile Project Management with TFS 2012 *Test Tools and Test Automation *Automated Builds and Deployments *Improving Developer Efficiency and Quality *Release Management / Change Management *DevOps - Supporting Applications in Production Environments *IBM or HP ALM Tools *Managing projects in a heterogeneous environment (e.g. Microsoft + Apple and/or Java, etc.)As always this group is about the community. There are a number of companies in Omaha with exciting and unique solutions around ALM and this is your chance to share these solutions with your community. Please let us know what you want to see or if you have something to present. Talks can be short or long, formal or informal. We are planning on having our bi-monthly meeting on the 2nd Tuesday on the odd numbered months (January, March, etc.). We are also looking into some alternative formats such as lunch meetings on the even months.
January 2013 MeetingJanuary 15th, 2013 6:00 PM - Farm Credit Services of America
**Intro:**Omaha ALM User Group Kickoff - 15-20 minute introduction of the group.
**Topic:**Creating a deployment framework with TFS and custom PowerShell cmdlets
As testing and release cycles continue to shorten for developers, automating application deployments becomes almost a necessity. TFS and WebDeploy provide some very powerful tools to simplify application deployments, but have limits to what can be done. An excellent way to extend the out-of-the-box deployment tools is with PowerShell, but that can carry a learning curve and become a maintenance headache very quickly. Enter custom PowerShell cmdlets - a way to hide all of that 'evil' PowerShell scripting and deployment logic from view, and at the same time, provide one location to maintain for any number of deployments. If done correctly, this can result in a fairly simple, yet very extensible deployment framework for any organization.
**Speaker Bio:**Andy is a Solution Consultant with Deliveron Consulting Services. He has over 10 years of .NET development experience in the Omaha area, most recently focusing on WCF service development and Team Foundation Server. Andy has been an active member of the Omaha .NET user group for many years and recently spoke at the Microsoft Visual Studio 2012 launch event in Omaha.
We look forward to seeing you there!