I made a change to the title to reflect that this is a request for Laravel. PHP has been requested in another area.
Wade Anderson - VS Code Team Member
We are adding a “Follow” toggle button on the work item button. When you follow a work item, you will receive an email for any change that happens to that work item.
@Timothy: you will only receive 1 email in that case.
In the new build system coming with TFS 2015 you can see the full history of the changes to your build definition. The feature that is currently missing is the ability to undo or rollback to a previous revision.
We expect to get the rollback deployed to our service in the next few months.
We still have rollback on our backlog. I hope to get it in over our next couple of sprints.
Has anyone tried the Visual Studio Color Theme Editor extension?
Matt added in the last version I believe an easier way to see what areas correspond to which colors. Take a look and let us know if this meets some or all of your needs.
Thanks Bart for letting us know that this one is completed.
As part of the process customization modernization effort, we’ll be bringing all the new value you’ve seen on Visual Studio Team Services to next version of Team Foundation Server as well. Existing customers will not be forced onto the new customization stack as part of upgrade. In the next version of Team Foundation Server you can choose whether you want to keep using the existing functionality with witadmin and xml editing, or you will have the opportunity to use the new functionality with process inheritance and WYSIWYG editing in the web. The new functionality is available in new collections or after migrating existing collections after upgrade.
@Brian, the next version of TFS Is the new major version of TFS
Folks -- I've merged the ideas. First time doing it, so hopefully I did it right. :-)
-Siddharth (Program Manager on TFS)
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.
@Shawn, it is true that we are asking that our customers try and embrace the new process customization features from here on out. The private preview for process customization is available but is subject to review to make sure the process template and the project are a good fit. If you are on TFS on-prem today and need to move to VSTS and you are blocked because of process customization, then you may be a good candidate. Please email us at firstname.lastname@example.org and someone will contact you to review your process template.
@Anyonymous: it is not possible to use Visual Studio (any version) to upload a process template to Team Services. We have created a new web experience to update your process: https://msdn.microsoft.com/en-us/Library/vs/alm/Work/import-process/customize-process
Couldn't agree more. Thanks for the comment. This is definitely something that is under review.
When we show the tree of iterations, it is sorted by name, not by date. Could you please explain where you see the iterations sorted by date?
I’m happy to announce that we’ve started work on enabling data import to VSTS from TFS. This will enable customers to detach and import a collection into a VSTS account. We’re hoping to have a private preview available in 2016 Q2. We’ll check back and update this item once we have more details to share.
TFS Program Manger
Sorry for any confusion that might have been caused. It looks like that item was a duplicate ask for data import. It was archived due to low votes and how long it went without getting any new votes. I have merged the suggestion you linked to into this one. We’ll be using this UserVoice item to convey our status on data import. We’re committed to providing a first class data import solution for Visual Studio Team Services.
TFS Program Manager
At this time high value features such as load test will be reserved for the higher end Visual Studio versions.
Thank you for your suggestion...i will pass it along to the Visual Studio Business Team for future versions of Visual Studio
Thank you for your suggestion! While we aim to respond to every suggestion, we are closing older ones that don’t have enough votes so newer ones from you can move to the top. If this suggestion is still important to you, feel free to open it again.
Raise as a ALM Community project. Did not meet triage #8 Ranger/PG value quadrant.
Looks like this was originally a Ranger suggestion...but is now dropped into "uncategorized".
If this was for the load test team i would still decline -but with a different response:
Excellent Suggestion and have passed this to the SQL Team for their consideration.
Visual Studio Load Testing is focused on doing Load and Performance Testing within the application development process and while we understand underlying services (such as databases) may need to be load tested directly have focused on making the platform extensible to solve these cases.
Thank you for the feedback. We will look at how best to address this.
Visual Studio Team
I believe this was shipped in the last sprint (Pratap can confirm) and now set using .runsettings
Just realized i am logged in as the Admin...
This is Charles Sterling and can be contacted directly at email@example.com
Can you share what formatting you are doing in Excel?
If the run data was available in charts like the build reports would that suffice?
(fwiw the last comment was by Chuck-accidently logged on as VS Admin)
We agree that the current load testing reporting needs to be improved. That said it probably won't be implemented with SQL Reporting. We are looking at what will solve this need and have a couple of options we are considering(note these are not exclusive to each other):
1. Reuse the Power BI solution the Microsoft performance team (in MCS) uses for their consulting efforts (tried, proven and works on the existing architecture)
2. Continue to invest in the Application Insights integration and have them handle the reporting
3. Integrate Load Testing to the existing Test Reporting we now building for the DevOps workflows.
See Chuck’s comment
(fwiw the last comment was by Chuck-accidently logged on as VS Admin)
Wanted to circle back to this request: At an uber level the request seems to be build an expert system for load testing...this is something we have looked at doing for Azure applications but in general probably not something we will be doing in the short term.
That said, tactically we are making improvements in this space in two ways
1. Integration with Application Insights -This work has started and will continue.
2. Improve the documentation - while there is a lot of content for load testing (in blog posts) we (I) will convert that into much more discoverable documentation (this work has just started)
Thank you for your feedback on this idea. We have reviewed this and determined first class integration of the sort would not be doable in foreseeable future. Azure powershell scripts/ custom tasks can be used to achieve the same objective. [Shashank Bansal – Microsoft PM]
The secrets can be saved along with the release definitions as RD/Environment variables and applied in the tasks for application with the deployments.
In case values need to be used from Key Vault, then it is recommended to use Azure powershell to query for the value of the keys and use as environment variable values.
We’ve added a basic search functionality for Visual Studio Marketplace. You can find more details regarding the same at the following link.
Thanks & Regards
Search is at top of the list on our backlog. We will share updates here, as we make progress.
You can easily reference any secret variable in any text input field with the $(varname) syntax. We currently do not propagate secret variables to the environment.
Double quotes should not be needed anymore. Also, if there is a packages folder in the sources directory, it is automatically searched for testadapters. Hence, any testadapter downloaded as a Nuget package will be used without any input. For others, you can specify the path as ‘$(Build.SourcesDirectory)\Fabrikam\NUnitAdapter’
Also, for up to date help and examples on the task, please see https://github.com/Microsoft/vso-agent-tasks/tree/master/Tasks/VsTest