Skip to content

EnableDefaultApplicationDefinition to false prevents Page's from working #1758

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
clairernovotny opened this issue Aug 31, 2019 · 1 comment
Assignees
Labels
Bug Product bug (most likely)
Milestone

Comments

@clairernovotny
Copy link

clairernovotny commented Aug 31, 2019

  • .NET Core Version: (e.g. 3.0 Preview1, or daily build number, use dotnet --info) 3.0 preview 8

Problem description:

If you set EnableDefaultApplicationDefinition to false, the other page XAML items get set to None instead of Page.

Actual behavior:

Expected behavior:
Page items should still be working

Minimal repro:

New WPF app, add a page.

Set EnableDefaultApplicationDefinition to false.

@rladuca
Copy link
Member

rladuca commented Sep 6, 2019

Thanks for reporting this @onovotny ! This was a regression from a prior change to support Visual Studio's reading of None items (see #685).

This fix was merged in both master and release/3.0 branches.

@rladuca rladuca closed this as completed Sep 6, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Apr 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Product bug (most likely)
Projects
None yet
Development

No branches or pull requests

3 participants