As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
We had 2 projects in TFS with same code base. 2 development teams were working on those. We are now merging the code to a one project and this is not an easy task to do manually.
Before starting development in separate we have not used any functionality that TFS provides to make this sort of work easy. Like branching, labeling or any other.
Can I get some guideline or best practices to plan this kind of work so we can adopt it in future to overcome this sort of work.
Link for a TFS guide for developers will also be helpful.
Thanks in advance.
The TFS Branching Guide is probably a good place to start. It will help you with structuring your source based on different usage scenarios
You might also want to look at answers to this questions: How to branch and merge in TFS
In regards to a "TFS guide for developers" the MSDN documentation is a good starting point. Beyond that consider the various books that have been published - there are some good ones out there.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Can anyone suggest me a good RoR open source project that covers a lot of Rails fundamentals but yet is simple, and most importantly has lot of features or atleast bug fixes that are yet to be implemented? I checked out a few like Spree, Substruct, etc. but could not zero in upon one, that is simple and has features to develop. I am not sure if any of them even had list of bugs to be fixed., though features will be better.
Check Diaspora, this is the Diaspora Github page.
Here is the List of open Issues
Here is the Diaspora Installation Guide
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
When building an MVC application from scratch without a pre-existing database, is using the code-first approach the best way to do it?
While most applications are database-centric, it is perhaps the schema rather than the database itself that governs how the app is built around it. As such, I think a code-first approach isn't too bad. It was late to the party (happened after database-first and model-first), but I think the code-first approach will become the norm soon.
What's your opinion?
First i think that this link can provide you with more information
In my opinion both of the approaches are useful. A developer/company needs to decide what is the best approach for there system, in some situation.
I think one good distinguish is Big and complex against small and simple applications
I think that developers or companies will prefer "DataBase First" approach when they builds complex application. In most cases DBA's will be needed in such project.
In those cases the project will include Store Procedures/ Triggers and maybe also a Data-ware house
In the other hand when you build a small application with one of small group of developers you probably prefer using "Code First" approach
again this is my opinion...
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
We are currently evaluating the mobile test automation tools for our reputed client. So far we have discovered that the following tools are popular. We want to perform POC of one open source and one licensed tool and perform the comparison study in terms of the best fitment to the client requirements. The client used iOS bid time.
Please let me know the Pros and Cons of each tool documented below and provide the recommendation. Based on your inputs, we will go ahead and perform the POC. The applications to be automated are enterprise applications. This is the first time we are doing the Mobile test automation, so please excuse if this question is too basic in nature.
List of tools we are aware of:
ZAP-Fix
Egg plant
M-eux
Fonemonkey
Appreciate all your inputs / assistance.
The better is to take a look at Frank or Calabash
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
As most IT companies use jira these days. Since it is a huge and complex application. But still it needs some improvements. Can someone share what improvements are needed for jira or any problem you faced while using jira?
I am asking this because in my last interview I was asked about this question, which I didnt expect, since I havent used jira so I don't know much about it. I need your help so I will be prepared in future interviews.
Atlassian tracks what users vote on at their own public JIRA instance. Here's a link to all their open JIRA issues sorted by the number of votes. Alternatively, you can read the JIRAAAARGH! chapter in my book Practical JIRA Administration.
~Matt
The list is long, and depends on what you are planning to use Jira for, such as:
who use it? (customers, developers, support, sales)
do you need svn/git support?
planning to use agile?
how do you want to open issues?
As well, while you might find many things missing, the big benefit of using Jira is that you can write your own code to achieve nearly everything.
To our needs, we found the following missing:
ability to rank issues
sending email for non Jira users
saving mail templates
24hrs issue notification
agile support (need to buy greenhoper to really support it)
front-end web forms for issue creation
You can also check Jira's new features requests and improvments
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
We've recently starting using TFS. Currently just for source control.
We're considering using work items instead of our current bug tracking system. I've heard that the work flow is customizable and would like to have a go at it.
A small example is that sometimes while working a bug, someone may decide that the product documentation needs updating, maybe to explain a workaround or if the bug fix caused a change to a screen layout, new screenshots would be required in the help file. I'd like it to work so that if somebody ticks a 'required docs' check-box on the work-item, after the bug is fixed and tested, the work-item would be automatically assigned to our documentation team.
I've heard TFS does support work-flow, but am struggling to find a suitable guide on how I'd go about customizing it.
Can you point me in the right direction? Or, have I misunderstood what's possible?
Welcome to the patterns & practices Team Development with Visual Studio Team Foundation Server project site! This guide shows you how to make the most of Team Foundation Server. It starts with the end in mind, but shows you how to incrementally adopt TFS for your organization. It's a collaborative effort between patterns & practices, Team System team members, and industry experts.
http://www.codeplex.com/TFSGuide