Agile bug fixing – what’s the preferred process for testing?
When a bug is fixed, the dev set its status to “resolved” and the bug is reassigned back to the person that created it. In our case this is usually the product owner – we don’t have dedicated testers.
TFS merging – how to track what changes go into MAIN?
I’m new to TFS branches, and have opted to set up a Dev and Main branch (ultimately there will be release branches too). I’m using TFS2012. My understanding is that I will work on the Dev branch on a day to day basis. When a bug is fixed or a user story is completed, I will merge Dev to Main, build, and give that to the tester.
Use TFS to track bugs from Production Support
I have just moved to a new company and they are using TFS 2010 (2012 in a couple of months) as their version control system and recently started to use it as a work tracking system for the developers.
Use TFS to track bugs from Production Support
I have just moved to a new company and they are using TFS 2010 (2012 in a couple of months) as their version control system and recently started to use it as a work tracking system for the developers.
Use TFS to track bugs from Production Support
I have just moved to a new company and they are using TFS 2010 (2012 in a couple of months) as their version control system and recently started to use it as a work tracking system for the developers.
Use TFS to track bugs from Production Support
I have just moved to a new company and they are using TFS 2010 (2012 in a couple of months) as their version control system and recently started to use it as a work tracking system for the developers.
Use TFS to track bugs from Production Support
I have just moved to a new company and they are using TFS 2010 (2012 in a couple of months) as their version control system and recently started to use it as a work tracking system for the developers.
Use TFS to track bugs from Production Support
I have just moved to a new company and they are using TFS 2010 (2012 in a couple of months) as their version control system and recently started to use it as a work tracking system for the developers.
What’s the most effective way to share code between .NET applications?
In our work, we have several different .net applications that share a lot of base functionality. We’ve built these applications using a clean n-tier architecture, but we’ve hit that moment where we realize that we’ve re-implemented the same functions several different times. Obviously this violates DRY, and we would like to correct that. We’re already using Nuget to some success for common glue code (wiring up IoC, logging, settings), but we also would like to share our data and business layers between all our applications. The idea is that the UI would only deal with the parts of the business layer it actually needs.
What’s the most effective way to share code between .NET applications?
In our work, we have several different .net applications that share a lot of base functionality. We’ve built these applications using a clean n-tier architecture, but we’ve hit that moment where we realize that we’ve re-implemented the same functions several different times. Obviously this violates DRY, and we would like to correct that. We’re already using Nuget to some success for common glue code (wiring up IoC, logging, settings), but we also would like to share our data and business layers between all our applications. The idea is that the UI would only deal with the parts of the business layer it actually needs.