This will be your chance to meet the members of the product team who work on the platform and tools you love and use on a day to day basis, to ask your questions and enjoy an hour full of discussion and demos on upcoming features and prototypes that we working on.
what's the roadmap of WPF?
Can't wait to hear how you are bringing access to the SwapChainBackgroundPanel to desktop WPF . . . .
2. WPF perf in virtual data presentation.
Any chance to see in the future Wpf released as Open Source?
Are the new UI debugging tools in VS 2015 going to be released for 2013 as an update or extension?
What is the future for WPF due to new Universal Windows Apps?
Would you say that WPF is still a viable choice for building applications now that there's Universal Apps just around the corner? Do you think it'd be a better idea to wait until Windows 10 is released, or keep learning WPF?
Is there a plan to bring Dependency injection into WPF as out of the box feature?
I mean real DI, like be able to do constructor (or at least property) injections into Pages, Controls, Converters, etc.
How many engineers are currently part of the WPF team ?
Seth is great as always!
@SimoneLocate​lli: Even before we get to Open Source, we need to make sure that we can develop WPF independently and not as a system component. We will continue to evaluate the feasibility of making WPF Open Source.
@Vynos:No, this is only for 2015.
One thing that I believe needs to be firmed up more is the nature of XAML serialization for WPF. The XamlObjectReader was left unfinished for WPF serialization and would be a good thing to have to propagate consistent future work in a Open Source environment. Failing this, making available the Blend serialization logic may also help.
We create .NET NuGet packages which have dependencies on native DLLs. We provide a single NuGet package that provides both x86 and amd64 versions of the native DLLs. We then use a build\<packagename>.targets file that will detect how the project is being built and copy the appropriate native DLL to the project's TargetDir. While that works great for EXE projects, it doesn't help with DLL projects which are in turn referenced from EXE projects. I really, really wished VS and/or C# projects had an "official" way to reference native DLLs/projects. This isn't that uncommon of a use case - managed project depends on native dll. Then perhaps NuGet could officially support this as well.
I feel that many customers felt lost when WPF kind of "disappeared" during the Windows 8 and Windows Store App hype. I appreciate the team's effort to clarify that WPF is still THE framework for Windows Desktop Applications. Nice.
@hillr: NuGet 3.0 is planned to support having native assets for different architectures.
Has Microsoft plans to make WPF multiplatform in desktop (Linux and Mac)?
Any plans on implementing x:Bind for WPF?
how about some more love for WPF/XAML 3D and port to universal apps too (would make good use when deployed onto HoloLens too I think)?
What guarantee it's going to be different??
Wonder how many developers feel like this??
Two thumbs up. WPF is a fantastic framework and it propelled me into the world of enterprise software development. I love it and I'm glad that all the rumors of it being "dead" are completely and utterly false.