Is WPF getting outdated with arrival of WinUI-3? [closed] - wpf

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
The community reviewed whether to reopen this question last year and left it closed:
Original close reason(s) were not resolved
Improve this question
Is WPF getting outdated with arrival of WinUI-3?
When it comes to Desktop Application development,
Is it about time to migrate to WinUI-3 completely leaving behind WinForm/WPF legacy ??

This WinUI 3.0 will not obsolete WinForms and WPF at all. Yes, .NET Framework 4.8 will be the last version of .NET Framework, but since we now have WinForms and WPF continuously developed on top of .NET Core, we should not worry.
These are the reasons: (and I think it's proven that WPF and WinForms aren't obsoleted)
WinForms and WPF are actively developed and supported on top of .NET Core since .NET Core 3.0. In .NET 5.0, we have full WinForms designer support in Visual Studio 2019 since 16.8.x, not just WPF on .NET Core since 16.7.x
Microsoft is in the development of evolving Windows desktop application development under one ambitious initiative as technology called Project Reunion. Project Reunion is open source on GitHub. The evolving Windows desktop app also means including WinForms and WPF as well.
See also the Project Reunion README: https://github.com/microsoft/ProjectReunion/blob/main/README.md
NOTE: The Project Reunion is also the umbrella of other Windows desktop UI initiatives/technologies such as WinUI 3.0, XamlIslands, UWP, and many more.

Related

Can I create Windows Desktop x86 application on M1 mac? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 months ago.
Improve this question
I own M1 MacBook and I need to create windows desktop app that will work also on windows surface and other intel machines as desktop application. I know there is WPF and windows forms (used them on windows machines in the past) to do that or some others like xamarin or whatever but is there way to create such app that will be cross platform ? Or can I use some virtual machine on M1 to create such app that can run on intel machines ? Is there any acceptable way to do it ?
If it's not possible using .net frameworks can I create windows desktop application using any other framework (using some other language like kotlin, java, C++ or whatever) on M1 mac?
After further research it look like it's not possible to create intel windows executable on M1 cpu at all. So basically you need two computers to do that.
As #adv12 wrote in comment looks like Avalonia is good choice but I
didn't tested it yet or .NET MAUI and also possibly Flutter desktop
could work. There is no way of building .net widow forms or WPF looks
like even on virtual machine as they also run in ARM mode.
Sure you can also go for old school Java JRE but thats kind of
outdated way and will not give great user nor developer experience I
believe.

Is it acceptable to ask the user to install ALL the windows update before running my application? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have a wpf application which requires .net 4 client.
I found that it crashes on a clean win7sp1 installation, but if I install all the updates (for windows 7 and for .net 4), my application runs very well.
So can I make a requirement that the user should install all windows updates?
The ideal requirement should be: win7 sp1, + kb2345xxx; but I don't know which kb is the the root cause of the fix of crash.
I don't see applications which requires all windows update, and I'm not sure if it's acceptable for the users.
I might be wrong but as far as I'm concerned Windows 7 doesn't include the .Net Framework 4.0, it ships with the .Net Framework 3.5
Furthermore, the SP1 doesn't include any .Net Framework upgrade, just hotfixes for the .Net framework 3.5. If your app requires a specific version of the .Net framework, then there's nothing you can do to make it run on lower versions, what you can do is add a check in the installer with some information about the required version of the framework so it fails gracefully rather than crashing
To answer your question, asking the user to download all updates is ok for an enterprise application. But, if you are targeting general users, then don't do that, many users have no technical knowledge whatsoever and will just ditch your app on the spot.
Resources
Windows versions vs.Net Framework
What's included in Windows 7 Service Pack 1 (SP1)
If your application requires .NET 4.0 with some other pre-requisites you might want to declare the required as Prerequisites while building your Setup and deployment project . Eg : here and here
The framework and any custom prerequisites can also be handled either by downloading from the vendor website or creating it yourself.

Best Framework for native apps [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I want to develope a native app (for Android and IOS, later Windows Phones, too. It will be designed for tablet computers like IPad etc.). It is an Enterprise application connecting to the database.
What is very important to me, is:
User Experience: It has to have this native Look-In and must be really attractive.
Performance: It has to have a high performance.
So with regard to the points I mentioned, I am looking for a framework offering the best components and controls for native development. Of course, it would be desirable to use an cross platform framework but for native apps.
I tried out Xamarin and read a bit about Appcelerator Titanium.
So referring to the criteria I mentioned, what is the best framework to develop my app?
Personally I would go for Xamarin. It's based on the mono project which is now quite mature. Xamarin have recently partnered with companies such as Microsoft and SAP.
I've generally found the troubleshooting to coding ratio higher for titanium than Xamarin. In my opinion Xamarin is the stronger platform; albeit a commercial product.

Is WPF suitable for Line Of Business software? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I do not know if this type of question can be asked on this site, please let me apologize if it is not relevant.
I'm currently thinking about starting the migration of an application developed in Visual Foxpro to VS. NET. I'm looking at Windows Forms and WPF, and I'm clear about the basics like the differences between them.
My specific question is whether, as of today, is WPF is an active and growing technology or another tool that died and will have no future support?
I am very interested in this information because I have some experience windows forms; studying WPF seems interesting, but I would not invest my time in a dead end.
I appreciate any information you can give me.
Of course it's suitable for LOB apps (much more so than the WinForms), and it is a growing technology being updated with every new version of the .NET framework, and with all the control vendors investing heavily into developing and updating their WPF controls.
Future is impossible to predict naturally, but WPF most certainly has a much better future than WinForms and it is, in my opinion, a number one choice for any new thick client project(s) on the Windows platform.
WPF is in so many ways vastly superior to WinForms but even if it was for data binding only it would still be easy to recommend over Winforms.
As a matter of fact, choosing WinForms over WPF at this time would be very similar to choosing VB6 over C# and the .NET Platform.
I used to work for an investment bank on Wall Street and many of the applications on the trading floor were WPF. And before I left, they were creating whole new suites of applications in WPF. This was in 2011.
Where I currently am, WPF is where all of the non-mobile projects are or are headed. And the applications are extremely critical; used worldwide.
Hope that helps answer any questions you had about whether people actually use it in the "real world".

risks of upgrading to Windows 8? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am a .NET/ C# desktop & web developer. My computer has fried, and I am getting a new one. I am being pushed in the direction of Windows 8 for the OS - although I am very hesitant to move from Windows 7. I am wondering if any developers have already done this upgrade, and if so, what headaches or pitfalls might I run into?
Specifically - I am asking if Windows 8 has any conflicts with any of the development tools I would be using: Visual Studio 2010/2012, IIS, ASP.NET Web applications, WinForms & WPF applications, DevExpress controls, etc. Should this be a seamless transition - has anyone run into any issues with these tools or otherwise something that I might not have thought of by upgrading my OS version?
Based on my experience it's basically the same for developers. Everything such as Visual Studio works the same, except that you got IE 10 and also every time you have to launch an application you have to go back to the tile screen, which I find annoying but I create shortcuts for them on the desktop. Then there isn't much difference at all.
There's apps like the free Classic Shell that will bring back some of the feel of earlier windows versions like the start menu.

Resources