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

WPF #316

Open
grahamehorner opened this Issue May 12, 2017 · 8 comments

Comments

Projects
None yet
3 participants
@grahamehorner

grahamehorner commented May 12, 2017

Please consider supporting WPF templates and/or that generate both WPF/UWP UIs for projects

@mrlacey

This comment has been minimized.

Show comment
Hide comment
@mrlacey

mrlacey May 12, 2017

Collaborator

What specific pages, features, frameworks, etc would you like to see with WPF support?
The more specific details you can provide the more it helps with planning and prioritization.

Collaborator

mrlacey commented May 12, 2017

What specific pages, features, frameworks, etc would you like to see with WPF support?
The more specific details you can provide the more it helps with planning and prioritization.

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas May 13, 2017

Member

@grahamehorner what is your scenario here. Supporting WPF would be a large engineering effort to keep parity. why WPF over UWP?

Member

crutkas commented May 13, 2017

@grahamehorner what is your scenario here. Supporting WPF would be a large engineering effort to keep parity. why WPF over UWP?

@grahamehorner

This comment has been minimized.

Show comment
Hide comment
@grahamehorner

grahamehorner May 13, 2017

IMO to make this tool really useful for my use case; I would need to create both WPF/UWP user interfaces with shared logic in a satellite assembly; as a large number of businesses have systems which run older operating systems that don't support UWP or have older applications that prevent the move to new operating systems.

You just need to look at the cyber attack and it's impact/number of systems effected to understand there is still a large user base running systems that can't run local UWP apps Windows 8/8.1

grahamehorner commented May 13, 2017

IMO to make this tool really useful for my use case; I would need to create both WPF/UWP user interfaces with shared logic in a satellite assembly; as a large number of businesses have systems which run older operating systems that don't support UWP or have older applications that prevent the move to new operating systems.

You just need to look at the cyber attack and it's impact/number of systems effected to understand there is still a large user base running systems that can't run local UWP apps Windows 8/8.1

@mrlacey

This comment has been minimized.

Show comment
Hide comment
@mrlacey

mrlacey May 16, 2017

Collaborator

That there are lots of older systems in use isn't of itself proof that people are continuing to build for them.

If WPF is needed what is required in terms of basic structure and pages? Are, for example, the WPF apps you're building using nav panels and pivots?

Collaborator

mrlacey commented May 16, 2017

That there are lots of older systems in use isn't of itself proof that people are continuing to build for them.

If WPF is needed what is required in terms of basic structure and pages? Are, for example, the WPF apps you're building using nav panels and pivots?

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas May 16, 2017

Member

@grahamehorner UWP is Windows 10 only. Based on what you're discussion, wouldn't the desktop bridge be a better option for you? We take a lot of dependencies on Win10 only features. What we made should work with WPF but for us to make a WPF template branch would require a lot of effort.

If you want to share a more detailed information on your customer base, please email me crutkas@microsoft.com. Would love to understand your data about your user population and their constraints. That will help us make more informed feature decisions.

If you're interested in contributing back and doing a PR with WPF, happy to see how this best fits in.

Member

crutkas commented May 16, 2017

@grahamehorner UWP is Windows 10 only. Based on what you're discussion, wouldn't the desktop bridge be a better option for you? We take a lot of dependencies on Win10 only features. What we made should work with WPF but for us to make a WPF template branch would require a lot of effort.

If you want to share a more detailed information on your customer base, please email me crutkas@microsoft.com. Would love to understand your data about your user population and their constraints. That will help us make more informed feature decisions.

If you're interested in contributing back and doing a PR with WPF, happy to see how this best fits in.

@mrlacey mrlacey added this to the Open Community Questions milestone Jan 2, 2018

@mrlacey

This comment has been minimized.

Show comment
Hide comment
@mrlacey

mrlacey Jan 2, 2018

Collaborator

Moving to Open Community Questions to see if there's (still?) demand for this

Collaborator

mrlacey commented Jan 2, 2018

Moving to Open Community Questions to see if there's (still?) demand for this

@mrlacey

This comment has been minimized.

Show comment
Hide comment
@mrlacey

mrlacey Jan 31, 2018

Collaborator

What project/navigation types would apply here?

  • classic/main menu?
  • ribbon menu?
  • blank / roll your own (like with current UWP support)

any others?

Collaborator

mrlacey commented Jan 31, 2018

What project/navigation types would apply here?

  • classic/main menu?
  • ribbon menu?
  • blank / roll your own (like with current UWP support)

any others?

@mrlacey

This comment has been minimized.

Show comment
Hide comment
@mrlacey

mrlacey May 22, 2018

Collaborator

Notes from recent discussion about this:

  • We need lots of planning here
  • Need clearly defined goals for doing this
  • Need to sync with plans from VS, XAML, & Mike H's team
  • Projects would default to targetting Win10 & include WinMD reference and have VS packaging project enabled.
Collaborator

mrlacey commented May 22, 2018

Notes from recent discussion about this:

  • We need lots of planning here
  • Need clearly defined goals for doing this
  • Need to sync with plans from VS, XAML, & Mike H's team
  • Projects would default to targetting Win10 & include WinMD reference and have VS packaging project enabled.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment