Creating tests.

Want to have multiple load tests that monitor the same set of other computers and record the same counter sets. Would like to be able to add or modify computers and counter sets in one place and have all the load tests use the new settings.

The window for managing load test results should be accessible from the main Visual Studio menus. At present it is only available by context menu or icons that are only shown with an open load test.

Import, export and removal of load test results. These operations can take a long time. They should be available as a separate program so other work can continue with Visual Studio.

Load test graphs

Want to save the specifications of a graph for use in multiple load tests or a way of copying a graph specifications from one test run to another. Load tests are often run before and after making some change to the system under test to gauge the effect of that change. So want the same graphs to be available from both test runs. Similarly, want to create the same graphs for comparing runs from different user loads and test mixes.

Altering the scale of a graph needs too many mouse clicks. The scale value is in a box that can be selected, but it cannot be edited. Allow scale changes to be made directly from the text box. Many graphs have the auto adjust scale selected, scale changes cannot be made until after this is unticked; adjusting the scale should be possible without needing to first untick the box, it should untick itself.

Graphs scales are only available in linear powers of 10. Logarithmic scales should also be provided.

There should be an option to select multiple counters on a graph and perform an operation on them. For example, to alter the scale on several counter to a new value.

When a line is deleted from a graph, the list should not be scrolled to show the top entry. Deleting several adjacent lines means having to repeatedly scroll down to find the next line to be deleted. This is made worse because only one can be deleted at a time; cannot select more than one line.

Currently there is no audit trail for TFS build configuration changes.

Provide an audit UI for changes made to a TFS build definition. The target audience would be administrators who are tracking down changes in build behavior over time to changes in the build definition.

The audit log should provide the following:
* the timestamp of the change
* something identifying the one who did the change
* It would be nice to see a summary of changes.

A rollback option would be even better and could be attached to the audit log (like it is for general TFS 2012 changesets).

I want the xml comment warnings for code generated by our developers, because it is in our coding standards to add xml documentation. However, we are using Coded UI, so there are many auto-generated code files included in our project, which clutters up the Error List (when treating warnings as errors) with thousands of errors we have no control over.

I want to be able to turn on the xml comment warnings in general, but disable the xml comment warnings for only code files that are auto-generated that we have no control over.

So, please add one of the following:
1. a way to disable the XML comment warnings for either all auto-generated code
2. a way to disable the XML comment warnings for certain file extensions (.Designer.cs).
3. Auto-generated code to include all xml documentation as to not cause the warnings

Any chance of adding to the eclipse plugin, the same button there is in Visual Studio (filter by solution button)?

If added I think it would be best to add it in the same place and situation when it shows in Visual Studio. In Visual Studio, when I'm about to do any check in I see this:

https://dl.dropboxusercontent.com/u/23242740/ScreenShots/2013-05-29%20Image_0002.png

And when I click the button to filter by solution I see the list shrunk to only the files from the current solution like so:

https://dl.dropboxusercontent.com/u/23242740/ScreenShots/2013-05-29%20Image_0003.png

In Eclipse button I would love similar feature, that would filter the files depending on the situation:

1) If there is nothing sellected in project explorer, but there is a file opened from this project, hitting this button will filter only files from this project

2) If there is a file, files, folder, folders, or whole project sellected, then hitting this button will filter only files from this project

3) If there are sellected files, folders or multiple projects before someone choosing the "check in" option, hitting the button will filter only files from those projects which files or folders, or project folders were sellected

As to where to place it, same place as it is in Visual Studio, so somewhere next to those buttons:

https://dl.dropboxusercontent.com/u/23242740/ScreenShots/2013-05-29%20Image_0001.png

sincerely
Lucas

It's a bit long but very easy to understand.
The following block statements would have members as well as the objects:
If
Select
While
Do
For
For Each
Try

First of all, some simple examples...
- the Exit and the Continue block-member-statements:
For i = 0 To 99
    Select Case i
        Case x
            For.Exit
        Case y
            For.Continue
    End Select
Next

- an example to control the outer For loop:
For i = 0 To 99
    For j = 0 To 99
        Select Case j
            Case a
                Select.For.For.Exit
            Case b
                Select.For.For.Continue
        End Select
    Next
Next

- same with short qualification:
For i = 0 To 99
    For j = 0 To 99
        Select Case j
            Case a
                For.For.Exit
            Case b
                For.For.Continue
        End Select
    Next
Next

------------------------------------------------

BLOCK MEMBERS:

- members of the For and For Each block objects:
For.<ParentBlock>
For.Exit
For.Continue
For.From (read-only)   //not available in For Each block
For.To   (read-only)   //not available in For Each block
For.Step (read-only)   //not available in For Each block
For.IsFirstIteration
For.IsLastIteration
For.Finish.Exited      (enumerator -1)
For.Finish.Skipped     (enumerator 0)
For.Finish.Completed   (enumerator 1)

- members of the Do and While block objects:
Do.<ParentBlock>
Do.Exit
Do.Continue
Do.IsFirstIteration

- members of the Try-Catch block object:
Try.<ParentBlock>
Try.Exit       (may not be important)
Try.Let
Try.CurrentException
Try.Result.IsNoException
Try.Result.IsLocalException
Try.Result.IsForwardedException

- members of the If-Else block object:
If.<ParentBlock>
If.Let

- members of the Select-Case block object:
Select.<ParentBlock>
Select.Exit
Select.Let
Select.Is (read-only reference of the test expression)
Select.FallThrough    (may not be important)
 
------------------------------------------------------ 
 
Other simple examples:
- an example to determine the finishing of a (functional) For loop:
Select For i = j To k
           If i = 100 Then
               Exit For
           End If
       Next
    Case For.Finish.Completed, For.Finish.Exited
        MessageBox.Show("There was iteration.")
    Case For.Finish.Skipped
        MessageBox.Show("There was no iteration.")
End Select
 
 
- simplified Try block with exception typelist after the Catch keyword:
Try
    PossibleException()
Catch ExceptionA, ExceptionB, ExceptionC
    MessageBox.Show(Try.CurrentException.Message)
Catch Else ' new explicit statement
    MessageBox.Show(Try.CurrentException.Message)
Finally
    If Try.Result.IsNoException Then
        MessageBox.Show("There was no exception.")
    End If
End Try
 
 
- assignment with the Let statements:
sNumber = Select Case(i) As String
              Case 1
                  Let "one"
              Case 2
                  Let "two"
              Case 3
                  Let "three"
              Case Else
                  Let "other"
          End Select
 
 
- assignment in a nested block:
myNumber = If(bln1) As Integer
               If bln2 Then
                   If.If.Let 1
               Else
                   If.If.Let 2
               End If
           Else
               Let 3
           End If
 
 
- an example to control the second (middle) For loop:
For i = 0 To 99
    For j = 0 To 99
        For k = 0 To 99
            Select Case k
                Case x
                    For.For.Exit
                Case y
                    For.For.Continue
            End Select
        Next
    Next
Next
 
 
- an other example with the to leave the outermost For loop:
For i = 0 To 99
    If b Then
        For j = 0 To 99
            Select j
                Case x
                    For.If.For.Exit
            End Select
        Next
    End If
Next
 
 
Advantages:
- in some cases would not need extra conditional structures with extra variables to control the flow in nested blocks, so some algorithm would run faster
- in some cases the GoTo jump-statement would be replaced when it is used to accelerate the run-time to leave nested blocks
- shorter and simplified code
- safer algorithm planning
- easier and safer maintenance
- easier code reading
- easy learning and using (block members by intelisense)
- reusable block feature (Let statement) like the lambda functions
- faster development
- there is no new reserved keyword
- etc...

In addition:
- it can be adaptable to C# also
- in C# the
  switch.break,
  do.break,
  for.break,
  while.break,
  statements would allow a safer and more sophisticated coding then with the general break statement