Attendees
Discussion
VS-extension
We can now use APIs to fetch current configuration from running VS instance.
We can’t for now do this per project.
We can enumerate e.g.:
EXE path, PDB path, path to project source files and
.vsprojfile.
GUI Functionalities clarifications that Nader Zouaoui will work on.
If EXE path is the same (except extension) toPDB file, we can skip specifying
--pdb_file <FILENAME>.We for now assume there’s only one EXE in the project.
We will rename radio button with “Target Name” and add to it dynamically text about current configuration, e.g.
..... ARM64|Debug. And:We should “disable” widgets for EXE selection.
There will be update to this widget naming convention as well.
We can warn if no PDB was generated with the project (or is not present).
TODO:
- Nader Zouaoui will add project based configuration search.
WPA-plugin
Some reworking has to be done due to how WPA framework is designed.
We’ve discussed base class solution with simple inheritance and common interface.
There’s an issue with current WPA-plugin after Alaaeddine Chakroun added third data cooker:
14:00:44:966 EventSource Error: ERROR: Exception in Command Processing for EventSource Microsoft.Windows.WPA: An instance of EventSource with Guid c35c6795-ffd9-4355-9ab4-ab5fe5acba52 already exists.
See:
New tickets for WPA documentation:
- Alaaeddine Chakroun WPERF-608 - Getting issue details... STATUS
- Alaaeddine Chakroun WPERF-609 - Getting issue details... STATUS