I had Docker Desktop installed for Mac Catalina last year, but I haven't used it until today, a day after updating to Monterey (from Big Sur) (I'm on a Mac Intel) when I downloaded the latest Docker Desktop dmg file (~500MB), which had me drag the icon to the folder, which I then chose to replace the existing .app file... but when opening the file (in /Applications), I get this new pop-up:
I've tried to search what this is actually going to do, and I can't tell; I use Cisco AnyConnect VPN sometimes for a project, and I'm afraid there'll be a conflict... but ultimately, I don't know what exactly I'm giving access to or if it's actually necessary. I just want to try Docker with Laravel Sail.
I know macOS over the last several years (since Catalina really) has changed filesystem stuff a lot and I end up going down StackOverflow rabbit holes trying to get things to work, so I'm hoping someone else knows how this works or has made it work and can advise.
I am using Android Studio 4.1.1 on Windows 10 20H2 with Hyper-V enabled on a computer with high DPI. Recently whenever I launch an AVD, the UI of the emulated device window becomes extremely large and impossible to use (as in the following screenshot). Other windows (including the AVD manager and the Android Studio itself) remains normal.
I have not used the emulator for a while, but I can make sure that the UI issue did not exist before I update my Windows to 20H2. I have also found similar questions on Stack Overflow (including this question), but the existing answers suggesting overriding its high DPI behavior does not work for me, because when I apply this setting, the emulator screen becomes so blurry that I cannot even recognize the texts on the screen.
How can I solve (or work around) this issue? Any help will be appreciated.
You can fix the scaling issue when using the Hardware rendering by simply making windows override the scaling setting. How?, it's very easy. Simply locate the .exe file for the emulator that you are using, (e.g. "qemu-system-armel.exe" for ARM and "qemu-system-x86_64.exe" for x86). To make sure which .exe file, just run the emulator then use task manager to locate the .exe file is running, see the screenshot. locate the .exe file using task manager
In my case it was in this location:
C:\Users[Username]\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe
I am using VS 2017 on mac with Unity3d. I have a project where different files and folders are soft linked (aliased) in to the project folder. The problem is that VS doesn't index those files, meaning that there is no autocompletion or visibility of other classes outside the current open file. The projects builds without problems, but there is no support when typing. Before High Sierra I could use hard links and that worked fine, but since High Sierra has apple file system, which doesn't support hard links, so I had to use soft links. Did anybody had this issue or knows where to look and what to try?
Thanks!
I have a Xamarin app that runs on Android, IOS and Windows 8.? It is essentially a “player” to display a proprietary document format. Formatting the documents so they look good on a small screen is a trial and error process. Essentially: Edit; Compile; Transfer to mobile; View; repeat;
To speed up this process, I am trying to build an emulator. I am using the Windows version of the app as a base for the emulator (because if I stay in Xamarin, I don’t have to rewrite all the code for Windows Forms)
The compiler is a Windows app. After compiling I know exactly where the file is located. When I run the emulator, it does not give me access to the Windows file system. I tried using PCLStorage Library. It stored the file here:
C:\Program Files\OpenSSH\home\30011765\AppData\Local\Packages\85930d70-750c-41a6-9b95-03faaed4159c_nh7s0b45jarrj\LocalState\ZDO\dev
I specified this part \ZDO\dev but have no idea how it selected the rest. Like why OpenSSH?
Question: Given this app is only going to run on Windows, is there a way to load a file as C:... ?
If not, is there another way for a Windows Forms App to share a file with a Xamarin Windows App?
I’ve spent several hours searching for a working example solution and have yet to find one.
EDIT: As it turns out, the issues described here were caused by an outdated version of the Adobe Air runtime. The Air app I had written was compiled for Air 2, but the computers were running Air 1.5. Updating the computers to Air 2.7 (the current version at the time of writing) fixed the problem. Unfortunately, running a newer Air app in an older runtime generates a misleading error. Beware!
ORIGINAL POST:
I'm building an Air app for internal use at my company. I need to install the app to a USB data stick, so that the installed app may be quickly moved from one computer to another. This works just fine on Macs, with the .air generated .app program running just fine on whatever Mac it is moved to.
When I do this on Windows, however, it only works on the computer that performed the initial installation of the .air file. Moving the stick to a different computer and running the program .exe results in an error message: "The installation of this application is damaged. Try reinstalling or contacting the publisher for assistance".
Is this the expected behaviour? Is there any way to run an AIR .exe on a USB data stick regardless of the computer that generated the EXE?
Just to be clear: I'm not looking to move the installer between computers, but the .exe that results from running the installer. I want to run the .air installer once, take the .exe result, put it on a data stick, and then run that .exe on any computer.
Simple recipe to make a portable Adobe AIR app
Ingredients:
A whole ziplock of Adobe AIR SDK, recently harvested from Adobe's server farm.
One .air package, fresh.
Command-line to taste.
Steps:
Extract the .air package with a 7-Zip blender.
In this folder bowl, whisk in the bin/adl.exe and runtimes/air/win from the SDK.
Take the META-INF/AIR/application.xml yolk and set aside.
Make sure to have adl.exe, win/ and application.xml in the folder casserole.
Add a pinch of adl -runtime win application.xml and let it simmer.
Optional: if you want shortcut sauce, just take note of the folder's location in your filesystem kitchen and re-write the parameters above so they have full paths to the win runtime and application.xml.
Finally, most .air will come with a baker's dozen .pngs in the icons directory. You can use an icon oven to grill these into a golden crispy icon.ico to be used in the shortcut sauce.
Bon appétit.
Compile the app to a native exe: http://www.beautifycode.com/compile-air-to-native-dmg-or-exe-files-with-ant. That should do the trick!
and http://help.adobe.com/en_US/air/build/WS789ea67d3e73a8b22388411123785d839c-8000.html
Update: for full stand alone operation look into shu-player, or http://dmartin.org/weblog/how-run-adobe-air-apps-windows-without-admin-rights
There's an easy method I always use (and I have never met the cases it hadn't worked).
Compile ".air" package, install it on your computer. After that, copy the following files from the app folder (keeping the directory structure intact) and run on any Windows machine which has the AIR framework installed.
Minimum set of files to copy:
\META-INF\AIR\application.xml
YourApp.exe
YourApp.swf
Once again, the limitation - your app can only be run on Windows.
In AIR 3 (in Beta right now), you can package an app as a "captive runtime bundle." On Windows this produces a folder that includes your app and the runtime itself. You can run the app from this folder without installation. Of course, some features won't work without installation. For example, registering file types for your app requires registry entries on Windows, so you would need an installer for that (or a utility program that set the required registry values would work, too)