Best way: restructure an existing Team Foundation Server (TFS) solution
In my department we are developing several smaller AddOns for some unified communication server. For versioning and distributed development we use a Team Foundation Server 2012.
Deliverables in a software development project
Following a standard framework of project management, for a software development project we will provide deliverables (documents and software) at the end of each month :
What type of projects should each of these projects be given their particular purposes?
I’m working in a creation of a new system that should be able to change the presentation layer without trouble, also be able to comport web-services, shop areas, internal control of data, creation of reports, multiple web portals, etc.
Best practices for sharing tiny snippets of code across projects
I always try to follow the DRY principle strictly at work; every time I’ve repeated code out of laziness it bites back later when I need to maintain that code in two places.
Solution with multiple projects and (GitHub) single issue tracker and repository
I have a Visual Studio solution with multiple projects:
Naming the project containing only interfaces [closed]
Closed 9 years ago.
Rigorous way to compare designs that support the same project
When having 4 different designs that can be delivered for a project and there is a strong difference of opinions on which design is preferred taking into account functional/non-functional requirements/effort etc is there some standard template/framework that can be used rigorously for comparison of the approaches?
I could come up with my own spreadsheet, I was interested if there is some existing framework that can be used in such cases?
Projects, Google , Information [closed]
Closed 1 min ago.
Why should I use MSBuild instead of Visual Studio Solution files?
We’re using TeamCity for continuous integration and it’s building our releases via the solution file (.sln). I’ve used Makefiles in the past for various systems but never msbuild (which I’ve heard is sorta like Makefiles + XML mashup). I’ve seen many posts on how to use msbuild directly instead of the solution files but I don’t see a very clear answer on why to do it.
Relation between projects and solutions in VS
We’re about to start with a new software and there are mixed opinions on the organization of software. I’d be delighted to hear what others might have to say in regard to the presented options as well as what other consideration one might refer to when making such a decision.