John SaundersJohn Saunders

My feedback

  1. 8,826 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      522 comments  ·  Visual Studio IDE » Project  ·  Flag idea as inappropriate…  ·  Admin →

      Thank you all for your continued feedback.

      In response to some recent feedback, we are happy to share that the SlowCheetah extension is officially supported by Microsoft and the Visual Studio team. Part of the reasoning behind moving it under the Microsoft repository on GitHub was to be able to maintain the extension moving forward. We understand many of you would love to see this integrated in the product. This idea is still under consideration and we will share the decision as soon as we can. We thank you for your patience.

      Thanks for the typo catch! We did intend to say the NuGet and VSIX name had been changed to Microsoft.VisualStudio.SlowCheetah.

      John SaundersJohn Saunders commented  · 

      I hope everyone realizes that almost every part of Visual Studio is an extension of some kind.

      Now, the fact that it doesn't get released with VS, that's an issue.

      John SaundersJohn Saunders commented  · 

      @random: I have never had a problem maintaining transform files. If it were painful, then nobody would want them.

      John SaundersJohn Saunders commented  · 

      @anonymous, why do want Microsoft to waste resources on a problem which already has a solution? Only with the withdrawal of support did it become necessary for Microsoft to spend resources.

      John SaundersJohn Saunders supported this idea  · 
    • 1,118 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        40 comments  ·  Visual Studio IDE » .NET  ·  Flag idea as inappropriate…  ·  Admin →
        John SaundersJohn 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 SaundersJohn 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 SaundersJohn 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 SaundersJohn Saunders shared this idea  · 
      • 54 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)

          We’ll send you updates on this idea

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

        • 1,674 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)

            We’ll send you updates on this idea

            Enabling the ability to move projects between collections is a feature that we’re committed to delivering. Since this feature is so highly requested, I’d like to provide some additional details behind why this has been pushed out.

            Simply put the issue is the cost to complete this feature. One way to think of it is that it’s XXXL in T-shirt sizing. A Team Project Collection (TPC) is a pretty rigid bounding container. It‘s the scope at which a number of “global” things exist.

            One such example is change set numbers. They start at 1 and count up in each TPC. That means projects in a TPC can’t have overlapping change set numbers. It also means that if you wanted to move TFVC projects between TPCs, you have to renumber all the change sets. That’s exacerbated by a requirement that change set numbers be time ordered. That means…

            John SaundersJohn Saunders supported this idea  · 

          Feedback and Knowledge Base