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 completely new to Mac OS and I have an application written in .Net Core codebase. Now all I want is to get it installed on Mac OS machines. My question is how can I create an installer (.DMG) file? At the moment My Visual Studio on Windows has created a .dll file with all other dependencies in the folder. Also for now most of the configuration values I have hard-coded but in the release build it has to be chosen by an end-user. So how can I prompt them for required directories? If you can provide me a link for documentation tool or any kind of suggestion would be greatly appreciated. At the moment if I want to run my application on Mac I have to use Terminal and then dotnet myApplication.dll in order to run application. My end goal would be to ask user for all required file paths and at the end create a System level Daemon (similar to windows service) to keep it always Alive. Would Xcode help in this situation? I already tried to open my .Net core project using xcode but it failed to load saying unsupported proect type.
Thanking in advance for your help!
If you wanted to use the standard macOS Installer to distribute your .net Core app, you would need to create a .pkg file. There seem to be ways to do this on the console or with Third Party Tools
sudo pkgbuild -install-location /Applications -component /path/to/your/application ./Desktop/YourPackage.pkg
There is an older manpage for pkgbuild, or you can try running man pkgbuild on your Mac.
I haven't tried this, but creating a .pkg is the normal way to install stuff on a Mac for applications where you can't just drag/drop the .app into the Application folder. (macOS applications are actually Directories with a special structure)
A .DMG is just a disk image - it doesn't "do" anything, it's just a container for files. You can create one with Disk Utility.
Got this Digital Keychain Photo viewer thingy. Comes with DPFMate which does not run under Windows 10. Does anyone know where DPFMate places the images on the keychain, so I could possibly write my own program to do the move?
i know this thread dates back to April but i have a device that uses DPFmate and it was packaged with it in memory. the software came with a windows and a mac version. fortunately most of the code is literally available in an uncompiled form in the mac app package. i have included everything from that package in a mediafire link. https://www.mediafire.com/file/ebyxepk013k18pd/Resources.rar
from what i gathered it loads a virtual drive from the machine using a SCSI connection driver of some sorts. i hope you can make sens of it more than me since i am not familiar with the programming language used.
going to install Mountain Lion OSX to multiple iMacs, to reduce the internet usage and get faster instalation id like to instal it from local source - already downloaded the instaler to one machine and extracted the DMG from installer
now - is there a way to connect the dmg the way so it is available as remote drive to the machine where I want to install (over LAN)?
with Disc Sharing on i know the CD/DVD can be shared, any knowledge whether it works for DMG files too? maybe disk utility somehow?
the catch is I have it downloaded on a new iMac 27" without a real drive and there is no "Disc Sharing" option in the sharing settings
Unfortunately, I know of no way to natively use i.e. PXE for Macs, so one would have to use Apples own methods. There is one that I did not test myself, using netboot and netrestore. Here is a link to a KB article:
http://support.apple.com/kb/HT4178
Maybe this is a good starting point for more research?
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)