John Saunders

My feedback

  1. 2,373 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      We are committed to supporting the ability to move projects between collections, however we’ve been unable to make progress on this feature. Unfortunately, the challenges highlighted in earlier posts are still present.
      I don’t foresee us making progress on this feature within the next 6 months. We will provide an update once we start planning for the second half of 2019.

      Whitney Jenkins
      Azure DevOps Program Manager

      John Saunders commented  · 

      I recently read about Azure DevOps being the replacement for VSTS. I didn't see any mention of TFVC. Perhaps that's how they plan to address this problem?

      John Saunders supported this idea  · 
    • 1,120 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        40 comments  ·  Visual Studio IDE » .NET  ·  Flag idea as inappropriate…  ·  Admin →
        John Saunders commented  · 

        @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?

        John Saunders commented  · 

        @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.

        John Saunders commented  · 

        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  · 
      • 63 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          John Saunders commented  · 

          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"?

        Feedback and Knowledge Base