Minimum version of Windows for Centennial Apps - desktop-bridge

What is the minimum version of Windows to be able to run Centennial Apps from the Windows Store?

Minimum version of Windows to use desktop bridge apps is Windows 10 Anniversary Update. This is Version 1607 (OS Build 14393). This is because desktop-bridge requires containers feature which is only available since Windows 10 Anniversary Update.
Keep in mind however that developer can target higher version of Windows through MinVersion field under TargetDeviceFamily tag inside AppxManifest.xml.
Here is example of targeting Windows 10 Anniversary Update:
<Dependencies>
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.14393.0" MaxVersionTested="10.0.14393.0" />
</Dependencies>
Source:
https://learn.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-run-desktop-app-converter#make-sure-that-your-system-can-run-the-converter
http://www.windowscentral.com/windows-10-anniversary-update-project-centennial-apps-store

Related

Can'n run the NET Framework 3.5 Service Pack 1 (Full Package) on Windows 11 with arm cpu, why?

I have a macbook M1PRO, and I need to debug .net2.0 and .net 3.5 codes in its Windows11 virtual machine, but I can't set up a code runtime environment。
I have installed .net framework 3.5 in the "enabling or disabling windows features" in the control panel, but its existence is still not recognized in visual studio.
enter image description here
enter image description here
If I don't use a simulated x64 virtual machine or another x64 computer, I just want to run all programs on one computer, how can I solve it?
If you create a x64 VM, then you have to install windows 11 (not arm based version).
then install visual studio for windows. (again, the non arm version).
At that point, you can develop with .net framework 2.0-4.8.
You can't create, run, use, enjoy, develop .net framework asp.net applications unless you running a windows VM, and using the windows version of VS.
You can ONLY run (and develop) .net core applications on arm based, or other computers, and NOT .net framework applications.
given that you looking to develop (or work on) a x64 .net framework, and quite a older version?
Then you have to create a x64 (not arm) based VM, and install the x64 bit version of windows (again, NOT the arm based version of windows). You then install Visual Studio for windows.
The above will thus allow you to develop and work on .net framework applications, such a as asp.net .net framework based application.

How to create a 64 bit desktop application (AIR) using Flash builder

I need to convert my adobe air application (using Flex 4.6.0.) into 64 bit desktop application (Mac OS and Windows).
Could you explain how to do ?
Indeed, macOS Catalina (macOS 10.15) won't support 32 bit apps !
So I need to find an alternative quickly.
Thanks for helping.
Best regard
In order to update to 64 bit, you will have to update your sdk. 4.6 version is very old (2012 maybe?).
First update your SDK to AIR 32.
Then you can use tag <architecture>64</architecture> in the application.xml file to force 64bit compile.
This works both in windows and mac for desktop apps.

Xamarin forms: Issue reported while submitting windows app to windows store

I have developed a Xamarin Forms(.Net standard) UWP app and submitted it to windows store, but the windows store team reject the app because of the following issue.
The app doesn’t install on one or more of the currently selected device families due to an unsupported minimum OS version. If the affected device family is not intended to be targeted, then please de-select the unsupported device family and resubmit the app. Otherwise, please change the minimum and/or target OS version that the app supports (https://learn.microsoft.com/en-us/windows/uwp/updates-and-versions/choose-a-uwp-version#choose-which-version-to-use-for-your-app)
My apps min and target versions are Windows 10 Fall Creators Update(10.0; Build 16299). I am targetting my app only for windows 10 desktop devices and windows 10 mobile devices. So what is the correct min and target versions for my app?
To Martin Zikmund:
If I downgrade target version to 15063 (Creators Update) my windows app build failed with the following error.
The solution for this error is changed the target version to Windows 10 Fall Creators Update(10.0; Build 16299), I found it here. If I changed the min and target version to Windows 10 Fall Creators Update the build will succeed.
You are probably trying to traget Windows 10 Mobile, which did not receive 16299 (Fall Creators Update) and got stuck on a sub-FCU build. To support it, you would have to downgrade to 15063 (Creators Update), but that means you can no longer use the latest versions of Xamarin.Forms which are targeting .NET Standard 2.0 which is not supported on 15063 and have to downgrade to version 2.X of Xamarin.Forms. You will also have to downgrade your library from .NET Standard 2.0 to Portable Class Library.
Practically this means that to be able to use the latest and greatest of Xamarin.Forms you will likely have to drop support for Mobile and target the other SKUs only. Judging by the numbers it is probably a good idea nowadays, as most users are on Windows 10 Desktop, iOS and Android anyway.

Install UWP package on Windows 8.1 Pro without developers license

With Xamarin.Forms I'm developing a mobile app. In Android I get this succesfully running on a device. I succeeded to create an app package from the UWP project and install it on my own Windows 10 PC. This is also my developing machine, so it's in Developer Mode by default. So it runs here without any problems.
My purpose is to get it running on Windows 8.1 Pro (tablet size). It just needs to consume the app. When installing the app by using the script, it's throwing the error that no developers license is found. On this device I didn't found anything to put it in Developers Mode, but it seems me that this is not needed, because it only consuming the app and no developing will take place on it.
It's is an internal app, so no need to place it on the Windows Store.
So my exact question: how can I install this app on this device without setting everything up for a Developer?
The answer would be no. Windows 10 has more new API and concepts that are not available on Windows 8.1. UWP app will not backward compatible to Windows 8.1. But WRT app will be Upward compatible to windows 10. It means that the windows 8 store app could run in windows 10. for more please refer Move from Windows Runtime 8.x to UWP.

Prevent to install WIX Setup on XP

I have a WIX setup MSI. I want to prevent it to install on WIN XP.
I was using the InstallPrivileges property of WIX but it did not solve my problem:-
<Package InstallerVersion="200" Platform="$(var.Platform)" InstallPrivileges="limited" />
How can i achieve this?
Priyanka, You are going in wrong direction.
InstallPrivileges attribute is use to specify the privileges required to install the package on Windows Vista and above.
Windows vista onward by default runs most applications with least privilege access (non-admin) in an attempt to keep both malicious virus code and inexperienced end users from damaging the system.
limited and elevated value from InstallPrivileges attribute specifies whether to use elevated privileges or not.
If you select Limited installer will run without Admin privileges and if you use elevated then your installer will ask for administrator privileges using UAC prompt.This attribute will be neglected if you are running it on windows xp (NOT SURE).
And Now to completely block your installer to run on windows XP then you need to use VersionNT property which will detect the version of the user's operating system.
The following sample demonstrates how to use this property to block installation of an application on operating systems prior to Windows Vista/Windows Server 2008
<Condition Message="This application is only supported on Windows Vista, Windows Server 2008, or higher.">
<![CDATA[Installed OR (VersionNT >= 600)]]>
</Condition>
Refer VersionNT values to choose for Which OS you want to block your installer.
refer for more info How To: Block Installation Based on OS Version

Resources