PerfView BuildLayout Command#2099
Merged
Merged
Conversation
Add the ability to build a fully extracted and self-contained PerfView layout. This is designed to avoid using the user-specific %appdata% installation of PerfView for scenarios where systems need to control updates and deployment of PerfView.
9fde8fa to
931c72c
Compare
cincuranet
approved these changes
Aug 22, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the
/buildLayout <path>command to PerfView.This allows users to build a self-contained fully-extracted version of PerfView that doesn't depend on
%appdata%. This is useful for certain deployment mechanisms where the deployed PerfView shouldn't impact PerfView in%appdata%.