- Visual Studio For Mac 2012
- Visual Studio For Mac 8.4
- Visual Studio For Mac Enterprise
- Visual Studio For Mac Build Windows App Download
You can use Visual Studio with the cross-platform Mobile development with C++ tools to edit, debug, and deploy iOS code to the iOS Simulator or to an iOS device. But, because of licensing restrictions, the code must be built and run remotely on a Mac. To build and run iOS apps using Visual Studio, you need to set up and configure the remote agent, vcremote, on your Mac. The remote agent handles build requests from Visual Studio and runs the app on an iOS device connected to the Mac, or in the iOS Simulator on the Mac.
Build your first C# console app. Develop a simple web application with Visual Studio for Mac. Build your first ASP.NET Core back-end service. Develop a simple back-end web service with Visual Studio for Mac. Cloud Development. Tomcat in the Cloud. Set up a Tomcat server in the cloud for free.
- Jun 16, 2017 Now in Visual Studio for Mac version 7.1, you can easily create distribution signing identities for use in your app publishing workflow without leaving the IDE: Wrapping Up. Visual Studio for Mac’s Fastlane integration makes it super easy for you to provision apps and devices directly from the IDE with just a few clicks.
- Jul 29, 2017 Basic tutorial on creating a Mac application using VS Mac. Button and label included in tutorial. Visual Studio Community edition https://www.visualst.
Note
For information on using cloud-hosted Mac services instead of a Mac, see Configure Visual Studio to connect to your cloud hosted Mac. The instructions are for building using Visual Studio Tools for Apache Cordova. To use the instructions to build using C++, substitute
vcremote
for remotebuild
.Once you have installed the tools to build using iOS, refer to this article for ways to quickly configure and update the remote agent for iOS development in Visual Studio and on your Mac.
Prerequisites
To install and use the remote agent to develop code for iOS, you must first have these prerequisites:
- A Mac computer running macOS Mojave version 10.14 or later
- An Apple ID
- An active Apple Developer Program accountYou can get a free account that allows sideloading apps to an iOS device for testing only but not for distribution.
- Xcode version 10.2.1 or laterXcode can be downloaded from the App Store.
- Xcode command-line toolsTo install the Xcode command-line tools, open the Terminal app on your Mac and enter the following command:
xcode-select --install
- An Apple ID account configured in Xcode as a signing identity to sign appsTo see or set your signing identity in Xcode, open the Xcode menu and choose Preferences. Select Accounts and choose your Apple ID, and then choose the View Details button. See Add your Apple ID account for detailed instructions.For detailed information on signing requirements, see What is app signing.
- If you are using an iOS device for development, a provisioning Profile configured in Xcode for your deviceXcode provides automatic signing where it creates signing certificates for you as needed. For detailed information about Xcode automatic signing see automatic signing.If you want to do manual signing, you need to create a provisioning Profile for your app. For detailed information on creating provisioning Profiles, see Create a development provisioning profile.
- Node.js version 12.14.1 and npm version 6.13.4Install version 12.14.1 of Node.js on your Mac. If you install the Node.js package, it should come with npm version 6.13.4. Other versions of Node.js and npm may not support some modules used in the remote agent
vcremote
, which can causevcremote
installation to fail. We recommend you install Node.js by using a package manager such as Node Version Manager. Avoid using the commandsudo
to install Node.js, as some modules can fail to install when usingsudo
.
Install the remote agent for iOS
When you install the Mobile development with C++ workload, Visual Studio can communicate with vcremote, a remote agent running on your Mac to transfer files, build and run your iOS app, and send debugging commands.
Before you install the remote agent, make sure you have satisfied the Prerequisites and completed the installation steps in Install cross-platform mobile development with C++.
To download and install the remote agent
- From the Terminal app on your Mac, verify that the Node.js version currently in use is the required version 12.14.1. To verify the version, run the command:
node -v
If it's not the right version, you may need to follow the Node.js installation instructions in the prerequisites. Then, restart Node.js. - After verifying the required Node.js is in use, run this command to install vcremote under that Node.js version:
npm install -g --unsafe-perm vcremote
The global installation (-g) switch is recommended, but not required. If you don't use the global installation switch, vcremote gets installed under the current active path in the Terminal app.During the installation,vcremote
is installed and developer mode is activated on your Mac. Homebrew and two npm packages,vcremote-lib
andvcremote-utils
, are also installed. When installation completes, it's safe to ignore any warnings about skipped optional dependencies.NoteTo install Homebrew, you must have sudo (administrator) access. If you need to installvcremote
without sudo, you can install Homebrew manually in a usr/local location and add its bin folder to your path. For more information, see the Homebrew documentation. To manually enable developer mode, enter this command in the Terminal app:DevToolsSecurity -enable
If you update to a new version of Visual Studio, you must update to the current version of the remote agent as well. To update the remote agent, repeat the steps to download and install the remote agent.
Start the remote agent
The remote agent must be running for Visual Studio to build and run your iOS code. Visual Studio must be paired with the remote agent before it can communicate. By default, the remote agent runs in secured connection mode, which requires a PIN to pair with Visual Studio.
To start the remote agent
- From the Terminal app on your Mac, enter:
vcremote
This command starts the remote agent with a default build directory of~/vcremote
. For additional configuration options, see Configure the remote agent on the Mac.
The first time you start the agent, and every time you create a new client certificate, you are provided with the required information to configure the agent in Visual Studio, including the host name, the port, and the PIN.
If you intend to configure the remote agent in Visual Studio using the host name, ping the Mac from Windows using the host name to verify that it is reachable. Otherwise, you may need to use the IP address instead.
The generated PIN is for one time use, and is only valid for a limited time. If you do not pair Visual Studio with the remote agent before the time expires, you will need to generate a new PIN. For more information, see Generate a new security PIN.
You can use the remote agent in unsecured mode. In unsecured mode, the remote agent can be paired to Visual Studio without a PIN.
To disable secured connection mode
- To disable secured connection mode in
vcremote
, enter this command in the Terminal app on your Mac:vcremote --secure false
To enable secured connection mode
- To enable secured connection mode, enter this command:
vcremote --secure true
Once you have started the remote agent, you can use it from Visual Studio until you stop it.
To stop the remote agent
- In the Terminal window
vcremote
is running in, enter Control+C.
Configure the remote agent in Visual Studio
To connect to the remote agent from Visual Studio, you must specify the remote configuration in the Visual Studio options.
To configure the remote agent from Visual Studio
- If the agent is not already running on your Mac, follow the steps in Start the remote agent. Your Mac must be running
vcremote
for Visual Studio to successfully pair, connect, and build your project. - On your Mac, get the host name or IP address of your Mac.You can get the IP address by using the ifconfig command in a Terminal window. Use the inet address listed under the active network interface.
- On the Visual Studio menu bar, choose Tools, Options.
- In the Options dialog box, expand Cross Platform, C++, iOS.
- In the Host Name and Port fields, enter the values specified by the remote agent when you started it. The host name can be the DNS name or IP address of your Mac. The default port is 3030.NoteSecurity scanning software for mac. If you cannot ping the Mac using the host name, you may need to use the IP address.
- If you use the remote agent in the default secured connection mode, check the Secure checkbox, then enter the PIN value specified by the remote agent in the Pin field. If you use the remote agent in unsecured connection mode, clear the Secure checkbox and leave the Pin field blank.
- Choose Pair to enable the pairing.The pairing persists until you change the host name or port. If you change the host name or port in the Options dialog box, to undo the change, choose the Revert button to revert to the previous pairing.If the pairing does not succeed, verify that the remote agent is running by following the steps in Start the remote agent. If too much time has passed since the remote agent PIN was generated, follow the steps in Generate a new security PIN on the Mac and then try again. If you are using the host name of your Mac, try using the IP address in the Host Name field instead.
- Update the folder name in the Remote Root field to specify the folder used by the remote agent in your home (~) directory on the Mac. By default, the remote agent uses
/Users/<username>/vcremote
as the remote root. - Choose OK to save the remote pairing connection settings.
Visual Studio uses the same information to connect to the remote agent on your Mac each time you use it. You do not need to pair Visual Studio with the remote agent again unless you generate a new security certificate on your Mac, or its hostname or IP address changes.
Generate a new security PIN
When you start the remote agent the first time, the generated PIN is valid for a limited amount of time—by default, 10 minutes. If you don't pair Visual Studio to the remote agent before the time expires, you will need to generate a new PIN.
To generate a new PIN
- Stop the agent, or open a second Terminal app window on your Mac and use that to enter the command.
- Enter this command in the Terminal app:
vcremote generateClientCert
The remote agent generates a new temporary PIN. To pair Visual Studio by using the new PIN, repeat the steps in Configure the remote agent in Visual Studio.
Generate a new server certificate
For security purposes, the server certificates that pair Visual Studio with the remote agent are tied to the IP address or host name of your Mac. If these values change, you must generate a new server certificate, and then reconfigure Visual Studio with the new values.
To generate a new server certificate
- Stop the
vcremote
agent. - Enter this command in the Terminal app:
vcremote resetServerCert
- When prompted for confirmation, enter
Y
. - Enter this command in the Terminal app:
vcremote generateClientCert
This command generates a new temporary PIN. - To pair Visual Studio by using the new PIN, repeat the steps in Configure the remote agent in Visual Studio.
Configure the remote agent on the Mac
You can configure the remote agent using various command-line options. For example, you can specify the port to listen for build requests and specify the maximum number of builds to maintain on the file system. By default, the limit is 10 builds. The remote agent will remove builds that exceed the maximum on shutdown.
To configure the remote agent
- To see a complete list of remote agent commands, in the Terminal app, enter:
vcremote --help
- To disable secure mode and enable simple HTTP-based connections, enter:
vcremote --secure false
When you use this option, clear the Secure checkbox and leave the Pin field blank when configuring the agent in Visual Studio. - To specify a location for remote agent files, enter:
vcremote --serverDir directory_path
where directory_path is the location on your Mac to place log files, builds, and server certificates. By default, this location is/Users/<username>/vcremote
. Builds are organized by build number in this location. - To use a background process to capture
stdout
andstderr
to a file named server.log, enter:vcremote > server.log 2>&1 &
Microsoft office software mac. The server.log file can assist in troubleshooting build issues. - To run the agent by using a configuration file instead of command-line parameters, enter:
vcremote --config config_file_path
where config_file_path is the path to a configuration file in JSON format. The startup options and their values must not include dashes.
Troubleshoot the remote agent
Debugging on an iOS device
If debugging on an iOS device does not work, there could be issues with the tool ideviceinstaller, which is used to communicate with an iOS device. This tool is typically installed from Homebrew during the installation of
vcremote
. Follow the steps below as a workaround.Open the Terminal app and update
ideviceinstaller
and its dependencies by running the following commands in order:- Ensure Homebrew is updated
brew update
- Uninstall
libimobiledevice
andusbmuxd
brew uninstall --ignore-dependencies libimobiledevice
brew uninstall --ignore-dependencies usbmuxd
- Install the latest version of
libimobiledevice
andusbmuxd
brew install --HEAD usbmuxd
brew unlink usbmuxd
brew link usbmuxd
brew install --HEAD libimobiledevice
- Uninstall and reinstall
ideviceinstaller
brew uninstall ideviceinstaller
brew install ideviceinstaller
Verify that
ideviceinstaller
can communicate with the device by trying to list the apps installed on the device:ideviceinstaller -l
If
ideviceinstaller
errors that it cannot access the folder /var/db/lockdown
, change the privilege on the folder with:sudo chmod 777 /var/db/lockdown
Then verify again if
ideviceinstaller
can communicate with the device.See also
-->By completing this walkthrough, you'll become more familiar with several options that you can configure when you build applications with Visual Studio. You'll create a custom build configuration, hide certain warning messages, and increase build output information for a sample application.
Install the sample application
Download the Introduction to building WPF applications sample. Choose either C# or Visual Basic. After the .zip file has downloaded, extract it and open the ExpenseItIntro.sln file using Visual Studio.
Create a custom build configuration
When you create a solution, debug and release build configurations and their default platform targets are defined for the solution automatically. You can then customize these configurations or create your own. Build configurations specify the build type. Build platforms specify the operating system that an application targets for that configuration. For more information, see Understand build configurations, Understand build platforms, and How to: Set debug and release configurations.
You can change or create configurations and platform settings by using the Configuration Manager dialog box. In this procedure, you'll create a build configuration for testing.
Create a build configuration
- Open the Configuration Manager dialog box.
- In the Active solution configuration list, choose <New..>.
- In the New Solution Configuration dialog box, name the new configuration
Test
, copy settings from the existing Debug configuration, and then choose the OK button. - In the Active solution platform list, choose <New..>.
- In the New Solution Platform dialog box, choose x64, and don't copy settings from the x86 platform.
- Choose the OK button.The active solution configuration has been changed to Test with the active solution platform set to x64.
- Choose Close.
You can quickly verify or change the active solution configuration by using the Solution Configurations list on the Standard toolbar.
Visual Studio For Mac 2012
Build the application
Next, you'll build the solution with the custom build configuration.
Build the solution
- On the menu bar, choose Build > Build Solution, or press Ctrl+Shift+B.The Output window displays the results of the build. The build succeeded.
Hide compiler warnings
Next we'll introduce some code that causes a warning to be generated by the compiler.
- In the C# project, open the ExpenseReportPage.xaml.cs file. In the ExpenseReportPage method, add the following code:
int i;
.ORIn the Visual Basic project, open the ExpenseReportPage.xaml.vb file. Rap beat making software for mac. In the custom constructor Public Sub New.., add the following code:Dim i
. - Build the solution.
The Output window displays the results of the build. The build succeeded, but warnings were generated:
You can temporarily hide certain warning messages during a build rather than have them clutter up the build output.
Hide a specific C# warning
- In Solution Explorer, choose the top-level project node.
- On the menu bar, choose View > Property Pages.The Project Designer opens.
- Choose the Build page and then, in the Suppress warnings box, specify the warning number 0168.For more information, see Build Page, Project Designer (C#).
- Build the solution.The Output window displays only summary information for the build.
Suppress all Visual Basic build warnings
- In Solution Explorer, choose the top-level project node.
- On the menu bar, choose View > Property Pages.The Project Designer opens.
- On the Compile page, select the Disable all warnings check box.For more information, see Configure warnings in Visual Basic.
- Build the solution.The Output window displays only summary information for the build.For more information, see How to: Suppress compiler warnings.
Display additional build details in the Output window
Visual Studio For Mac 8.4
You can change how much information about the build process appears in the Output window. Build verbosity is usually set to Minimal, which means that the Output window displays only a summary of the build process along with any high priority warnings or errors. You can display more information about the build by using the Options dialog box, Projects and Solutions, Build and Run.
Important
If you display more information, the build will take longer to complete.
Change the amount of information in the Output window
Visual Studio For Mac Enterprise
- Open the Options dialog box.
- Choose the Projects and Solutions category, and then choose the Build and Run page.
- In the MSBuild project build output verbosity list, choose Normal, and then choose the OK button.
- On the menu bar, choose Build > Clean Solution.
- Build the solution, and then review the information in the Output window.The build information includes the time that the build started (located at the beginning) and the order in which files were processed. This information also includes the actual compiler syntax that Visual Studio runs during the build.For example, in the C# build, the /nowarn option lists the warning code, 0168, that you specified earlier in this topic, along with three other warnings.In the Visual Basic build, /nowarn doesn't include specific warnings to exclude, so no warnings appear.TipYou can search the contents of the Output window if you display the Find dialog box by choosing the Ctrl+F keys.
For more information, see How to: View, save, and configure build log files.
Create a Release Build
You can build a version of the sample application that's optimized for shipping it. For the release build, you'll specify that the executable is copied to a network share before the build is kicked off.
Visual Studio For Mac Build Windows App Download
For more information, see How to: Change the build output directory and Build and clean projects and solutions in Visual Studio.
Specify a release build for Visual Basic
- Open the Project Designer.
- Choose the Compile page.
- In the Configuration list, choose Release.
- In the Platform list, choose x86.
- In the Build output path box, specify a network path.For example, you can specify
myserverbuilds
.ImportantA message box might appear, warning you that the network share that you've specified might not be a trusted location. If you trust the location that you've specified, choose the OK button in the message box. - Build the application.
Specify a release build for C#
- Open the Project Designer.
- Choose the Build page.
- In the Configuration list, choose Release.
- In the Platform list, choose x86.
- In the Output path box, specify a network path.For example, you could specify
myserverbuilds
.ImportantA message box might appear, warning you that the network share that you've specified might not be a trusted location. If you trust the location that you've specified, choose the OK button in the message box. - On the Standard toolbar, set the Solution Configurations to Release and the Solution Platforms to x86.
- Build the application.The executable file is copied to the network path that you specified. Its path would be
myserverbuildsFileName.exe
.
Congratulations! You've successfully completed this walkthrough.