@James, just to be certain we understand you, do you expect to have problems if you use Visual Studio 2012 to develop ASP.NET 4.0 applications which will run on Windows Server 2003? Can you say what problems you expect?
The lack of a service pack more strongly affects those who can't test and debug their application in the target environment. Are you unable to test on Windows Server 2003?
@Reinhard Ostermeier: I believe I understand your concern, but I don't understand why you can't use VS2012 to build .NET 4.0 applications, then deploy the application to the Windows XP machine which has the special hardware installed on it.
Perhaps I wasn't clear. You can develop in VS2012 and support XP. The only thing you can't do is be assured that finding no problems when you debug on your VS2012 machine implies there will be no problems when running on XP. You will need to do QA on a machine running only .NET 4.0.
That is the only restriction I have seen. Have you seen something else, or is this the restriction which will prevent you from upgrading to VS2012?John Saunders shared this idea ·
62 votes6 comments · Visual Studio Team Services » Dashboards and Reporting · Flag idea as inappropriate… · Admin →
We are excited to announce a preview of the new Analytics Marketplace Extension(https://marketplace.visualstudio.com/items?itemName=ms.vss-analytics) is coming in the next major release of TFS
Please refer to our reporting roadmap(https://docs.microsoft.com/en-us/vsts/report/analytics/reporting-roadmap) for additional information on the roadmap for reporting in TFS and VSTS
If you want more votes, you should substantiate your assertions. For instance, would power pivot and rally handle all of the existing TFS reports? For what scenarios are there "better, easier, and more powerful ways to do reporting"?
2,278 votes105 comments · Visual Studio Team Services » Administration & Licensing · Flag idea as inappropriate… · Admin →
We are still committed to delivering the ability to move projects between collections, however we’ve been unable to make additional progress on this feature. The challenges highlighted in the earlier post are still present and unfortunately this work is still on hold. We recognize this is a highly requested / needed feature, however I don’t foresee us making additional progress on this feature within the next 6 months. We will provide an update once we start planning for the second half of 2018.
TFS & VSTS Program ManagerJohn Saunders supported this idea ·