Name: Xamarin.Forms
Owner: Xamarin
Description: Xamarin.Forms official home
Created: 2016-03-18 15:52:03.0
Updated: 2018-01-17 12:16:04.0
Pushed: 2018-01-17 17:41:18.0
Homepage: https://xamarin.com/forms
Size: 38493
Language: C#
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
Xamarin.Forms provides a way to quickly build native apps for iOS, Android, Windows and macOS, completely in C#.
Read more about the platform at https://www.xamarin.com/forms.
Platform/Feature | Package name | Stable (2.5.0 branch) |Nightly Feed MyGet (master branch)
———————–|——————————————-|—————————–|————————-
Core | Xamarin.Forms | 
| 
Maps | Xamarin.Forms.Maps | 
| 
Pages | Xamarin.Forms.Pages | 
| 
If you want to use the latest dev build then you should read this blog post :
Add the nightly feed to your nuget sources or add a NuGet.Config to your app with the following content:
l version="1.0" encoding="utf-8"?>
figuration>
ackageSources>
<clear />
<add key="xamarin-ci" value="https://www.myget.org/F/xamarinforms-ci/api/v2" />
<add key="NuGet.org" value="https://api.nuget.org/v3/index.json" />
packageSources>
nfiguration>
NOTE: This NuGet.Config should be with your application unless you want nightly packages to potentially start being restored for other apps on the machine.
Change your application's dependencies to have a * to get the latest version.
VS 2017 is required for developing Xamarin.Forms. If you do not already have it installed, you can download it here. VS 2017 Community is completely free. If you are installing VS 2017 for the first time, select the “Custom” installation type and select the following from the features list to install:
Summary > Optional select the Windows 10 Mobile Emulator.Summary > Optional select Xamarin Remoted Simulator, Xamarin SDK Manager, Intel Hardware Accelerated Execution Manager (HAXM)We also recommend installing Xamarin Android Device Manager This will use the HAXM tools installed above and allow you to configure Android Virtual Devices (AVDs) that emulate Android devices. If you already have VS 2017 installed, you can verify that these features are installed by modifying the VS 2017 installation via the Visual Studio Installer.
Upon opening the Xamarin.Forms solution, you will find that there are a number of errors and warnings under the Error List pane; you can resolve this by changing the filter of Build + IntelliSense to Build Only. At this point, you should be able to successfully build the solution.
By default, the Xamarin.Forms.Controls project does not have a configuration for various API keys to access certain features on each platform (e.g. maps). When building the solution the first time, a controlgallery.config file will be generated inside that project, which looks like this:
UWPMapsAuthKey:
You will have to obtain your own API keys for each of these services, inserted directly after the identifier (e.g. UWPMapsAuthKey:abcdefghijklmnopqrstuvwxyz). You can find out how to obtain each of these as follows:
UWPMapsAuthKey at https://www.microsoft.com/maps/create-a-bing-maps-key.aspxDue to the way that Android works, the maps API key cannot be injected at runtime. As a result, you will have to add this key to the MapsKey.cs file under Xamarin.Forms.ControlGallery.Android/Properties:
[assembly: Android.App.MetaData("com.google.android.maps.v2.API_KEY", Value = "INSERT_KEY_HERE")]
You can find out how to obtain a Google Maps API key here.
Make sure you have Nuget.exe 4.0 or above and the latest dotnet core sdk (2.0.3). On OSX you should specify the platform in the msbuild command (/p:Platform=iPhoneSimulator)
nuget restore Xamarin.Forms.sln
msbuild Xamarin.Forms.sln
If you change or add a public API on Xamarin.Forms the associated documentation should be updated and pushed as part of the pull request. This will also be needed to create a local nuget if you want. We rely on mdoc that is shipped in the repo on the tools folder. After building the .sln on Windows run:
./update-docs-windows.bat
on OSX execute:
make docs
We follow the style used by the .NET Foundation, with a few exceptions:
private keyword as it is the default accessibility level in C#.Tools > Options and navigating to Text Editor > C# and selecting the “Keep tabs” radio option. In Visual Studio for Mac it's set via preferences in Source Code > Code Formatting > C# source code and disabling the checkbox for Convert tabs to spaces.Source Code > Code Formatting > C# source code and changing the Desired file width to 120.We use GitHub Issues to track issues. If at all possible, please submit a reproduction of your bug along with your bug report.