With the December 10th deployment, we have released our first phase of our rollout plan to deliver process customization to Visual Studio Team Services. You can now add your own fields, and change the layout of the work item form.
We’ll continue marching down our backlog and add more customizations until we reach full parity with what we have in TFS. This is going to take some time and you can read more about our plans in this blog post: http://blogs.msdn.com/b/visualstudioalm/archive/2016/01/11/process-customization-futures.aspx.
Update 2/14/2017 – I am happy to announce that we have updated the SlowCheetah extension to work with Visual Studio 2017 and 2015. You can install the extension from the VS marketplace: https://marketplace.visualstudio.com/items?itemName=WillBuikMSFT.SlowCheetah-XMLTransforms
We are also in the process of adding support for additional project and file types. For the latest development news for the extension, check out the GitHub repo: https://github.com/sayedihashimi/slow-cheetah
Please let us know if you run into any issues by reporting them at the issue tracker on SlowCheetah’s GitHub page.
Note: if you installed the preview extension for Visual Studio 2015, please be sure to remove it before installing the new one to avoid conflicts.
Happy to announce.. what a smuck
Wtf, they are still insisting as keeping it as an extension. We should all drop vs
M$ has NO RAD tool, since it killed off VB6 and VFP.
If it were open-sourced, a cost-free VB6 would grow and smother M$''s fat-ba$tard child, .NET. Same goes for VFP and $QL $erver.
So, dream on.
You killed off your decent RAD tools, VB6 and VFP.
No one wants the time-sucking trash heap of .NET.
Hello supporters of this suggestion
We are considering the possibility of a solution to this issue for a future release of Visual Studio.
One possibility under discussion is that the default folders would not be created until they are first used, giving users the opportunity to specify their own location at that moment, and have it stored in the (existing) preferences location.
Feedback on the thread below is welcome,
Program Manager, Visual Studio IDE Team
this is why i have a seperate folder for MY documents and leave the documents folder to be trashed by MS and every other person/company that thinks this is a good folder to dump ****. autodesk is another big offender in this regard
1 voteAnonymous shared this idea ·