file.copyAsync(myLocalfolder, file.name, Windows.Storage.NameCollisionOption.generateUniqueName).done(function (newfile) {
console.log(newfile.name); // <-- SHOWS THE SAME NAME EVEN THO IT CREATED A COPY WITH A DIFFERENT NAME BECAUSE THERE IS ALREADY A FILE WITH THE SAME NAME IN THAT SAME FOLDER.. WHYYYYYY? PLS dont tell me MICROSOFT created this function without returning
the NEW NAME.. if so it would be the MOST r***culous flaw ever. I think even a CHILD would expect it returning the new name in case it created a new copy with a new name
});
