Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
All you requisite weight depend on the actual operation environment. Very difficult to give a "general" weight. For example: > Desktop Client for Multiple OS If you development spans across multiple OSes it is "critical", othewise "little impact" or "nice to have". > Devlopment API Do you plan to extend it? In which way? If you don't it's not very important, if you need to integrate it with many other tools may be critical. > Multiple developers to check out same file Again, this depends on your development. C files? They can easily merged. Flash? I don't think so. > Promotion Model: Example: Bat - Dev - QA - Prod With any tool you can usually build a promotion model. In CVSNT you can do it moving tags, other products may have ad-hoc features. > Integration with Visual Studio .NET 2003 & 2005 Again, it weight depends on how much of your development is made with VS. Although most VCS tools can be integrated via SCC providers. The support depends on the provider. > Integration with Rational Web Developer See above. > Code label/tagging support That's a must for any VCS, or it is pretty useless. > Branching > Merging Again, a feature every good VCS offer. The real issue is how easy it to perfom them. Much depends on your branch/merge strategy, however. > Reporting Capabilities What kind of reporting? It's a very wide area. > Performance over WAN/VPN Again, a critical issue if you really need it. -- Luigi D. Sandon