dotnet / dotnet/project-system

Enable XBAP specific WPF Property pages

Open
#70 0 comments 0 reactions 0 assignees View on GitHub
Feature-XAML Parity-Legacy-Feature Triage-Approved
Dominant language
C#
Stars
1k
Forks
415
PR merge metrics
No merged PRs in 30d

Description

_From @davkean on March 23, 2016 18:9_

WPF flavor swaps in property pages, we need to decide what we'll do around this:

```
if (pageReplacements == null)
{
// Populate the page replacements list
pageReplacements = new List();
if (IsHostInBrowser)
{
// For XBAPs, swap in the new security and signing pages:
pageReplacements.Add(new PageReplacementItem(
"{DF8F7042-0BB1-47D1-8E6D-DEB3D07698BD}", // Security property page
"{00a2c8fe-3844-41be-9637-167454a7f1a7}" // WPF Security property page
));
pageReplacements.Add(new PageReplacementItem(
"{F8D6553F-F752-4DBF-ACB6-F291B744A792}", // Signing property page
"{e4b54061-084d-4484-9d21-ecae95a78a56}" // WPF Signing property page
));
}
if (GetLanguage() == Language.VisualBasic)
{
// For all VB WPF apps, swap in the new application page:
pageReplacements.Add(new PageReplacementItem(
"{8998E48E-B89A-4034-B66E-353D8C1FDC2E}", // VB Application property page
"{00aa1f44-2ba3-4eaa-b54a-ce18000e6c5d}" // VB WPF Application property page
));
}
}
```

_Copied from original issue: dotnet/roslyn#10017_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.