Why are Windows 'APP's so much harder to code than a Windows Forms application?

Question

For example I have been smashing my head against a wall trying to save an image file from a share target, the best help I can find is the below code:
https://social.msdn.microsoft.com/Forums/en-US/65a61679-0da8-4109-8a69-b918be351dfa/how-to-save-a-bitmap-image-from-a-share-target?forum=winappswithcsharp&prof=required
But in a 'normal' application I can do what I need to do with:
using System;
using System.Drawing;
namespace Project1
class Class1
static void Main()
Image photo = Image.FromFile("C:\\Temp\\oldphoto.png");
photo.Save("C:\\Temp\\newphoto.png");
Why do the APPs take so much more code to do something like save a file to disk?
Mediocre Access 2010 | (Baby) Beginner C Sharp | OK at Active Directory (2012) | Fragmented understanding of DNS/DHCP | Laughable experience with Group Policy | Expert question asker on MSDN Forums

Answer 1

It is a good question!
If you need 100 lines of code to save an image it is like a Java program:
- complicated
- not fun to develop with
I think the main problem is that Microsoft release 2 new libraries each year. On the most cases, if you try to compile it with an old library it works, but the app crashes with unexpected errors. It is always harder to develop for Windows and there
are always more libraries to use.
So it begun to be normal, to find a W8-store-app-library and use it in Silverlight, to add missing functionality.
It is a jungle and it seems that Microsoft too doesn't know anymore what library should be in the msdn-help. Some times, if you search for something, you finish on a library that can't be added to your project.
This is the reason, because your question will probably never be answered!