I have created a Visual Build Professional 8 script that uses the "System" > "VisBuildPro Project" step to call another build script. I browsed to the correct build script to be run for the step in the Project tab of the properties the "VisBuildPro Project" step and clicked apply but when I run the main script the step does not call the correct build script. It keeps calling the script I created.
Has anyone had this issue and do you have a fix?
The problem was that I have a 64-bit OS and originally the 32-bit version of Visual Build Pro was installed on the machine then the 64-bit version was installed which caused issues when launching another script. I was able to discover this when I ran Visual Build Pro from the command line for my script. I uninstalled both versions and just reinstalled the 64-bit version and this fixed my problem.
Related
I am on a PC Visual Studio CE 2022 attempting to archive and deploy for iOS. I am using the following command:
dotnet publish PopUpShop.Mobile.Maui -f net7.0-ios -c Release /p:ServerAddress=192.168.1.XXX /p:ServerUser='username' /p:TcpPort=58181 /p:ArchiveOnBuild=true
The process builds and connects to my Macbook but then throws this error:
C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\16.1.1477\tools\msbuild\iOS\Xamarin.Shared.targets(1738,3): error : Could not find Microsoft.iOS in /usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/16.1.1477/
I am not quite sure where it is looking for /usr/local/share.... I assume that is on the Macbook.
Do I have to install that version of the SDK on the Macbook? If so how do I do that? (Not a mac user). I tried in Terminal
dotnet add package Microsoft.iOS.Sdk --version 16.1.1477
but it wants to add that to a specific project.
Xcode 14.2 is still working on and it's not supported yet by Visual Studio c. You could check the release note here Visual Studio 2022 version 17.4 Release Notes.
As an alternative, you could now try downgrading back to Xcode 14.1 and build the project. If you still have questions, feel free to ask.
Hope it works for you.
The problem was I was missing the /p:_DotNetRootRemoteDirectory='/Users/{mac_os_username}/Library/Caches/Xamarin/XMA/SDKs/dotnet/' parameter. For some reason it was not part of the cli string I copied. The error message doesn't help either, sends you down a rabbit hole.
I am trying to build a MAUI app on Mac OS using Visual Studio and I got an error that says to run dotnet workload install wasm-tools so I try running it in the Mac terminal in the app project folder and I get the following error.
Workload installation failed: One or more errors occured. (The given key 'Microsoft.iOS.Sdk' was not present in the dictionary.)
It runs on Visual Studio on Windows for the Android version. I've ensured that everything is updated, including the Mac itself and Visual Studio.
Please be noted that it is a known issue that is being tracked in dotnet workload fails with KeyNotFoundException after updating SDKs, you can try to run dotnet workload uninstall ios, after which you can try to run dotnet workload restore which finally should work.
I have a cross platform xamarin project running on Windows VS 2017. I have a mac which I am connected to with the latest version of Xcode and VS installed with the xamarin versions matching. When I go to build the project, I get an error: "The Xamarin Build Agent is not running on the Mac. An active Build Agent is required to perform the build".
I know for sure that I'm connected, and that the xamarin versions are the same on the mac and windows. I followed all the steps here: https://developer.xamarin.com/guides/ios/getting_started/installation/windows/connecting-to-mac/troubleshooting/
I'm at a loss here, and any help would be greatly appreciated.
I have the same problem, i found this solution on xamarin forum
https://forums.xamarin.com/discussion/100185/the-xamarin-build-agent-is-not-running-on-the-mac
I hope this of help
I've got the error :
"The Xamarin Build Agent is not running on the Mac. An active Build Agent is required to perform the build".
Tools -> extension and updates
Find Xamarin.Apple SDK
Click Revert.
Everythings come back to normal.
Thanks for solution
Benoist
I'm developing a mobile app with Visual Studio Tools for Apache Cordova CTP 3.1 in VS 2013. I have configured everything according to the MSDN specifications here Install Tools to Build for iOS. I am able to build the app and run the remote simulator (as described here Run Your Apache Cordova App on iOS).
My problem is there is no output from the build back on the Windows machine where I have Visual Studio. More than that, there is no .ipa file created on the Mac either. I can find the build at /Users//remote-builds/builds/ but that's all. I can open the project in XCode for instance, but that's not what I want.
I want the final package file that I can install on test devices and eventually publish to the store. How do I get that?
Also my goal is to setup a TFS build definition so I can get a build each time I commit changes. I need to get that output file to the drop location of my build.
From within VS, you will have to choose "Remote Device" or "Local Device" as your debug target and then "build" to get an IPA back.
Also, refer to TFS build does not copy Cordova project output for instructions on how to setup TFS for CI workflow.
I have a problem with finding stuff about how to compile cordova apps from visual studio (desktop) on my macbook without parallels and similar things. I googled that stuff, but I found nothing relevant, or with parallels/vmware stuff.
I added some insight what I want to do in my comments, yet pasted it here:
nope, I mean, I have two devices: the desktop, where I have Windows 8.1 and a macbook pro mid 2012. And I want to (start a) build the cordova app from my desktop, but run it on my macbook (via iOS simulator). I don't want no dual booting, no virtualisation, just start the build from visual studio and finish the build on osx
Here are the steps:
Prerequisites
Mac OS X Mavericks
Xcode 5.1 and Xcode command line tools
An active iOS Developer Program account with Apple, with iOS provisioning profile and signing identity configured in Xcode
Node.js installed on the Mac
Installation
Run the following command from the Terminal app on your Mac:
sudo npm install -g vs-mda-remote
sudo npm install -g ios-sim
Setting Up the Remote Agent for Building
To start up the agent, run the following command:
vs-mda-remote --buildDir <server-build-directory>
This will start the agent in build server mode. An additional command line parameter is required to start up the agent for personal use with the iOS Simulator that will be covered later.
Setting up the Remote Agent to Support Starting the iOS Simulator
If you are using the remote agent on a personal Mac (vs a shared Mac build server), you can configure the agent to support launching the iOS Simulator on your Mac from Visual Studio.
As mentioned previously, the ios-sim node module is required globally to enable starting up the iOS Simulator from Visual Studio.
The build server should then be started with the command line option --allowsEmulate=true:
vs-mda-remote --buildDir <server-build-directory> --allowsEmulate=true
When these requirements are met, the app can be deployed from Visual Studio to the simulator on the Mac running the agent.
For more details, the documentation contains a section called "Remote Build & Simulation Agent for iOS".