White Hat Vs. Black Hat Search engine optimization
Most builders are conversant in the Debug and Launch configurations in most resolution templates in use. It seems obvious to use the Debug configuration when building your project for debugging and to use the release configuration when constructing your project for launch. What could also be much less clear, though, is what’s truly happening if you switch configurations, or how so as to add your personal customized configurations.
At the moment, we’re going to dive slightly deeper into the world of construct configurations to see how they'll vastly enhance your build occasions and productivity. Simply said, configurations are a set of challenge properties. In the default Debug configuration, as an example, debugging will be enabled, while in a Release configuration it is not going to be.
How Can I Edit a Configuration? The template creates a easy Android app with a button that counts clicks. It has two configurations arrange by default, Debug and Release, and one platform, AnyCPU. These are simply names that don’t have any inherent meaning, except being reflective of when the configuration must be used.
We’re going so as to add two new configurations named DebugDevice and DebugEmulator later on. These will enable us to rapidly set the desired mission options/properties when debugging to a device (ARM) or an emulator (x86). Every will solely construct for the architectures needed for a gadget or an emulator, decreasing build time during growth. First, let’s see what’s completely different between the two default Debug and Release configurations.
To do so, open the challenge properties by proper-clicking on the challenge in the answer explorer and selecting “Options” (VS for Mac) or “Properties” (VS for Home windows). As soon as the venture choices/properties are open, you’ll see configuration and platform fields in the direction of the top with drop-down lists to pick which configuration and platform you need to see the property settings for. The drop-down might not be there (VS for Mac) or disabled (VS for Home windows), which signifies that the settings on the settings web page you have got selected are international, i.e. they are going to apply to all configurations and platforms.
Normal settings web page in VS for Mac and in the appliance settings web page in VS for Home windows. A lot of the variations within the undertaking settings for the default Debug and Release configurations are in the Android Construct / Android Options settings web page shown above. Open the challenge options/properties and select the Android Build (VS for Mac) / Android Options (VS for Home windows) on the left.
Ensure Debug is selected at the top in the configuration drop down. Word that the “Use Shared Mono Runtime” on VS for Mac or “Use Shared Runtime” in VS for Home windows is chosen, as nicely as the “Fast Assembly Deployment” (VS for Mac) / “Use Fast Deployment” (VS for Windows) possibility.
In VS for Mac: In the Android Construct page choose the “Linker” tab. You will note the “Linking Behaviour” is set to “Don’t Link” for Debug configuration and “Link SDK assemblies only” for Release configuration. In VS for Home windows: Within the Android Options page scroll to the “Linker Properties” part. You will notice the “Linking” possibility is about to “None” for Debug configuration and “SDK assemblies only” for Release configuration.