We are excited to announce SlowCheetah 3.0, which now supports JSON transforms. As well, this extension is released under Microsoft so the nugget and vsix name has been changed to Microsoft.VisualStudio.SlowCheetah. The gallery extension supports VS 2015 and VS 2017.
Where did you see that show cheetah is deprecated?
Does SlowCheetah take care of this? http://visualstudiogallery.msdn.microsoft.com/69023d00-a4f9-4a34-a6cd-7e854ba318b5
I agree. It would be awesome to use config transforms during debugging, etc instead of just during deployment.
Hello everyone and thank you for the feedback. We are actively investigating ways to improve how Visual Studio handles project content. This suggestion falls into that category. Unfortunately, we will not be able to address this feedback for the Visual Studio 2015 release. We will update the community when our plans in this area have gained more clarity.
Visual Studio – VS IDE Project and Build Team
@Nathan Black that's an amazing idea! We are building an angularjs app that has _nothing_ to do with asp.net. That being said, I love Visual Studio and want to continue using it as my daily development but I don't want to dictate to others which OS/IDE (if any) they should use. I'm considering treating the project as a web site instead of a web application which I think might solve the problem in a round-about way.
This would really be great for teams that develop on different platforms for the same project. I love Visual Studio on Windows and others on my team use Sublime Text on a Mac. This would definitely make it a much better experience.
To a certain extent this is available in VS 2013 with the code indicators.http://blogs.msdn.com/b/bharry/archive/2013/06/03/visual-studio-2013.aspx
This was archived by mistake. I’m sorry for the noise.
Program Manager, VSTS
With TFS 2017 and VSTS, you can see a history of changes for a build definition. You can select a previous version from that history and restore the definition to that version.
We are now beginning to look at how we can manage definitions entirely in source control so that you can use the same branching and policies for definitions as for the rest of your code.
Indeed that is what I was thinking about.
@stavn it is just a xaml file. If I need to change the build definition then I update the file and check it in.
You can always store the build definition file in source control. This is what I do.
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.
They called it Enterprise Agile.
It looks like this is coming in TFS 2013!!
I agree that if code is commented out, delete it. That's what source control is for.
I’m pleased to say we are looking to include this feature in a future release of Visual Studio. In line with manycomments in this thread, we’re planning to provide a means to change the modifier from Ctrl+Click to other options for those who would like to keep Ctrl+Click for selecting words.
Program Manager, Visual Studio Editor Team
I'm more of a keyboard guy. I use F12.
Think of the App_Start folder that is popping up all over the place. Also, I like to keep extension method classes in an Extensions folder but would really like to have the namespace be the root namespace. Great idea.
I'm out of votes but this is an AWESOME idea!
Build A succeeds -> Build B is triggered.
Personally I'd prefer to set this up in Build B to "watch" Build A then have Build A specify that Build B should be triggered.
Thank you for using Visual Studio and for your commitment to improving it. We are currently evaluating whether we will be able to include this in the product. We will provide an update soon.
Awesome ideas for the dependency graphs....
@Cesar this has long been a standard of tab-driven apps like web browsers.
We are planning to have a public preview of the VSTS Symbol service in the summer this year. The service will allow users to publish and store symbols in VSTS and allow debuggers to retrieve symbols from the service.
Great idea. No votes left :(
I could get behind that one too.