12 votes0 comments · Visual Studio Team Services » Administration & Licensing · Flag idea as inappropriate… · Admin →
73 votes4 comments · Visual Studio Team Services » Administration & Licensing · Flag idea as inappropriate… · Admin →
MSFT did this in the 90s and got sued. I just don't see it happening.
This is a real major limitation! Why would there be a hard limit? This should at least be overridable for certain cases.
As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.
I finally got around to playing with VStudio 2012 & TFS 2012. I would say the agent installer is great! Thanks for the improvement there!
The one snag I ran into which may be outside the scope of this feature is I am having trouble upgrading the Test Controller.
#5 Well, the actual domain controller itself wasn't, but the networking between the domain controller, the VMHost and the other vm's was confusing. If we had template dc and template vms for this setup, would help a ton.
#3 A blog post would be ok, but may be hard to find for other users. I was able to get around this eventually but it was a huge learning curve. You know, maybe a sample script or 2 in the MSDN documentation showing how its used may be even better. We just had no samples to go by. We need to have samples like "Hey if you are deploying using MSDeploy with Lab Mgmt do this." or "If you are going to deploy databases using database projects, here is a sample using Northwind db, step 1, step 2, step 3 with actual scripts"...
It would be very convenient to have scripts that are ready to go or templates of the most common tasks when doing environmental builds and deploy. To me these would be a script to deploy an msdeploy website or a basic copy script with the basic parameters already in place. Having samples like this helps us to understand how the scripts should work. Another example would be a database compare and deploy for a specified environment. Right now there is nothing to go by and it took me a long time to figure things out.
As for #4, in the test manager, in the lab mgmt tab, we can't tell what version of our app is running. And with 12+ environments it can be easy to lose track.
As for isolated networks. This was so hard to just get up and running that we just quit on it. Having a premade domain controller would be nice as a template.
If VB had the basic refactoring that C# has, all would be good. Thats what this recommendation is talking about. There is no extract as method in VB.