Launch app converted by DAC - desktop-bridge

I've converted my app using Desktop App Converter.
Installed appx from step 1.
Launched cmd.exe and entered the following command:
"C:\Program Files\WindowsApps\MyApp_5.1.30.6486_x86__z4vxg0xscex6e\MyApp\myapp.exe"
Got the following error message: Access is denied.
Why?
What is the proper way to programmatically launch DAC converted app including any EXE inside of it?

Once installed, you can launch the app from the app list in the start menu.
If you need to be able to launch the app from a command box, you will need to declare an appExecutionAlias in the manifest, as described here:
https://learn.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-extensions#alias

Related

Xamarin Forms UWP start application with parameters

I have a Xamarin project (Droid and UWP(Fall Creators)) and
I would like to start the UWP application by passing parameters.
I found how to start the application from command :
explorer.exe shell:AppsFolder\TestCommand_7ngdmc6chkqa8!App
Now I am looking to add parameters.
I found some examples for UWP but it doesnt work with Xamarin.
Has anyone ever tried and found a solution?
Thanks
The command line explorer.exe shell:AppsFolder\TestCommand_7ngdmc6chkqa8!App could not be used to launch UWP app with parameter. Windows Store apps aren't designed to run from the command line and there isn't a straightforward way to launch them from the command line. Although you can find some blogs about the above command line, but we could not recommend that.
Currently, It is a better way that launch UWP app with Windows.System.Launcher APi. But you need to register the protocol for your app at first.
After registered the protocol, you could also launch the App in the command prompt.
start [protocol name]:[parameter]
Example
start microsoft-edge:http://www.google.com
For more you could refer Launch an app for results.

Desktop app converter fails to run, with: "The data area passed to a system call is too small"

I have installed Desktop App Converter from the Windows store.
When I try to run the app (literally just launch it), I get the message:
[Window Title]
C:\Program Files\WindowsApps\Microsoft.DesktopAppConverter_2.0.2.0_x64__8wekyb3d8bbwe\DACTileLauncher.exe
[Content]
C:\Program Files\WindowsApps\Microsoft.DesktopAppConverter_2.0.2.0_x64__8wekyb3d8bbwe\DACTileLauncher.exe
The data area passed to a system call is too small.
I have tried running the Troubleshooter for Windows Apps, it tells me that "Windows Store cache and licenses may be corrupt" and tries to fix them, but running the troubleshooter a second time gives the same issue.
Each time I try to run the Desktop App Converter, I get 2 errors in Event Viewer:
%1: Cannot create the Desktop AppX container for package %2 because an error was encountered configuring the runtime.
%4: Cannot create the process for package %1 because an error was encountered while configuring runtime. %5
... both from AppModel-runtime
Any ideas how I can troubleshoot from here?
If you have problems with the Microsoft DAC you try this new converter, it is much easier to use, it has a GUI (no command line), built-in support for digital signing and allows you to customize the list of files that get inside your AppX.
Also, you can generate AppX packages for applications which do not (cannot) install silently.
It runs on Windows 7 too, not just Windows 10 (recommended).

Project Run Issue in Meteor?

I start to run Meteor project in command prompt as shown below
C:\Users\dsk>e:
E:\>cd abc/red
E:\abc/red>meteor //Here I got the below error then click any button the error popup and close the error popup and doesn't runmeteor project
E:\abc/red> //here some times get this (or) some time gets another
(or)
Exited with code: -1073741819
=> Your application is crashing. Waiting for file change.
So please see the error and suggest me what to do?
Meteor isn't fully & officially supported on windows.
You could file an issue with the unofficial Windows Meteor project: https://github.com/sdarnell/meteor
Or you could use a virtual machine or vagrant to use the official Meteor under ubuntu, see https://gist.github.com/gabrielhpugliese/5855677

Qt: Cannot execute '': The requested operation requires elevation

I am not able to run the application the Qt creator. It complains the following error:
Cannot execute '': The requested operation requires elevation
My .exe file has a Windows administrator shield symbol on it. Do I need to make a project settings changes? I am extensively using Qt File library for doing some file operations.
What's your executable's file name? Without an embedded manifest, windows tries to be smart and wants to run executables with "install", "update", "setup", "patch", etc. in the file name as administrator. It even checks for those names within words such as "autoupdate".
The problem is that qmake/mingw doesn't embed those manifests, while MSVC does. If someone has a clean solution to that problem, I'd be interested to learn about it.
If application you develop require administrator privileges, you cannot simply run it from Qt creator, started under non privileged account.
You can run your Qt creator as Administrtor.
Or you can start your application from QtCreator using runas utility.
But in this case you would not be able to see debug output in QtCreator console window and debug application.
If the name of the exe file has some words (update, patch, ...), the Windows UAC ask for admin privilegies. The only solution is that the project generates an exe without these words.
See this: Qt Creator create exes with admin privilegies

How do I debug XPC Services in XCode 4?

I added an XPC Service to my project and I would like to set breakpoints and inspect variable contents in the debug area in XCode. Breakpoints that I set in the service's code are not recognized (obviously, the debugger is attached to the main apps process. How and I attach the debugger (manually or automatically) to the XPC Service process after my main app launches it? Is there some way to run the service alone and send it messages without it being launched from the main app?
Debug -> Attach To Process -> By Process Identifier (PID) or Name...
Type in your XPC service process name. The next time launchd starts up your XPC service, Xcode will attach.
I am actually not sure how to attach the debugger. But you can still use "NSLog" for debug output on the console. Then start the "Console.app" in "/Applications/Utilities/Concole.app". Depending on your system language this app may have a different name (it's localized). It shows ALL NSLog outputs from all Applications which are running including your xpc-services.
It's not the debugger, but you will get informations out of your service.

Resources