Home

Known issues

A) UNABLE TO FIX: Double new lines in ReleaseNotes.txt when accessing through VS -> Extensions

Tried double space, slash, linux endline,
.

B) DONE: Verify crash when resizing goes to 0

C) DONE: On some machines SDD/Rotational detection maybe is not working (no prof for this, just need to check)

D) DONE: Fix CPU inconsistency. In header there is "Cores: 2" in summary there is "Done (53% of 4 CPUs)"

E) DONE: Assert/Crash/Empty PBM pane, even when pane is visible.

F) DONE: "Clean Solution" change/break graph.

G) First Experience, First run: First run

.

.

Planned changes to v1.8

Goal for v1.8 is: A) Save reports for comparison after improvements B) Reveal bottlenecks and their causes

List of planned changes to PBM in Random order

---

1) DONE: Create unit test to cover whole save to .csv

2) DONE: Create unit test to cover whole save to .png

3) DONE: Solution name in saved file name

4) DONE: Save Critical Path to .csv

5) DONE: Dark theme for menu

6) DONE: Marking critical path

7) DONE: Add Solution name and time to graph

8) DONE: Add number of cores in CPU graph

9) DONE: Add traditional/SSD info in HDD graph

10) Verify if plugin doesn't slowdown build

Partially done. 1.7+ doesn't slow more than 1.7 (verified 2019-01-01)

11) DONE: Collecting CPU and HDD performance points in constant time intervals

Done in 1.7+ at 2019-01-01

12) DONE: Saving "Build Timing" to csv

"Build Timing" Page

Only VS English is supported!

13) DONE: Better organize files and directories in Git

14) REJECTED: Add Help page

15) DONE: Remove trailing zeros (0) in front of build project order number (e.g. "001>")

16) DONE: VS2019 support

17) REJECTED: Show Slider

Show vertical slider even if not necessary - Gantt looking strange without it
Unable to achieve this. All subwindows in VS works in the same way as current implementation of PBM window, so rejected.

18) DONE: Show Elapsed Times for projects in progress

19) DONE: Polishing

• DONE: remove comment about division by zero in catch{}
• REJECTED - when crash happen there is nice call stack that allow to track problem: add try{} catch{} for PBM initialization

20) DONE: Polish Gantt chart

Now, Gantt is pixel-perfect: Margins, spacing, no blur (background drawn first), graph not cross vertical line, text not overlap vertical line, border around (for save and on screen) and so on.

21) DONE: Update Readme.md

22) DONE: AsyncPackage

30) Run "Code Analysis" and fix errors/warnings

31) Update marketplace page

.

.

.

.

Planned changes to v1.9

Goal for v1.9 is: Usability and more data collection

List of planned changes to PBM in Random order

---

1) Copy to Clipboard

2) Sorting

3) Save to .csv

• save projects build time
• save CPU and HDD performance data
• save all project dependencies

4) Shortcuts

5) Menu as standard menu not as pop-up context menu

6) Ability to change counters resolution (e.g. in context menu)

8) Showing "Build Timing" under tool tip

"Build Timing" Page

9) Pass BuildOrderNumber as "uint" not as "int"

10) RAM usage

12) Collecting CPU and HDD performance in separate thread and in constant time intervals

14) Show Elapsed Times even for very short project builds

15) Double click on Gantt

Double click on Gantt move to Output/Build window to line with Task Performance, or project start line

16) Enable/Disable "Build Timings" in pup-up context menu

17) PBM installation should enable "Build Timings"

18) Are we able to check how much time pre- and post- build step for C# project took?

19) Collect "Build Timing" in other languages than English

20) Capture "Build Timing" for "Target" and "Project" categories

21) Add "Build Timing" remark to .csv report

When solution has c++ project and "Build Timing" is Off, add remark to .csv about enabling it

22) Introduce Codding Standard and update sources

Names format for Methods, Method Arguments, Class Members, Local Variables

Method arguments as interfaces (currently Class.Method(Dictionary<int,int> arg), should be Class.Method(IDictionary<int,int> arg)

23) Enable/Disable CPU and HDD Graphs

Do we need this?
If slowdown is minimal, probably this is over-investing that need to be maintained.

.

.

.

Ideas for v1.10

Possible Goal for v1.10 is: Ability to collect data on servers (compilation without GUI)

---

1) Can PBM be run on VS without GUI to collect data?

Compilation Server usage case

2) Store summary time for solution for all builds on particular machine

Compilation Server usage case

3) What "calls" means in "Build Timing" output report?