No description, website, or topics provided.
C# Visual Basic JavaScript GLSL Ruby CSS Other
Latest commit 21e5b50 Sep 26, 2017 @conceptdev conceptdev fix incompatible xibs
Permalink
Failed to load latest commit information.
AnalogClock Fixed some brief descriptions Apr 2, 2015
AsyncAwait [ios] update min os version to 8 Jul 18, 2017
Azure [ios] update min os version to 8 Jul 18, 2017
BackgroundLocationDemo fix incompatible storyboards/xibs Sep 5, 2017
BluetoothLEExplorer [ios] update min os version to 8 Jul 18, 2017
BouncingGame Fix metadata file Sep 8, 2016
CCAction [CCAction] Fix Roslyn complains May 30, 2016
CCAudioEngine Checked in coin time/fruity falls songs (they're not used in the samp… Apr 17, 2016
CCDrawNode Removed usage of the now-obsolete DrawDot. Feb 19, 2016
CCRenderTexture Fixed title on CCRenderTexture guide. Jun 2, 2016
Camera [ios] update min os version to 8 Jul 18, 2017
CameraMovement3DMG Fix metadata file Sep 8, 2016
CoinTime Added SFX and Music to Coin Time. Jun 11, 2016
ContentControls fix incompatible storyboards/xibs Sep 5, 2017
DataAccess Fix metadata file Sep 8, 2016
EmbeddedResources Fix metadata file Sep 8, 2016
FruityFalls 42875: fixed spaces on conde Feb 21, 2017
GLKeysES30 [ios] update min os version to 8 Jul 18, 2017
GoneBananas Fixed link to Gone Bananas. Feb 18, 2015
LivePlayer fix incompatible xibs Sep 26, 2017
MWC [mwc] remove deprecated sample Nov 13, 2015
ModelRenderingMG Fix metadata file Sep 8, 2016
ModelsAndVertsMG Fix metadata file Sep 8, 2016
MonoGameTvOs Added image to MonoGame tvOS project. May 1, 2016
MultiThreading [ios] update min os version to 8 Jul 18, 2017
Notifications Bump minimum target version to iOS 6.0 Aug 26, 2016
Phoneword [ios] update min os version to 8 Jul 18, 2017
Profiling removing profiler walkthrough sample temporarily. Mar 14, 2017
RazorTodo [RazorTodo] Remove unused googleplayservices reference Jun 19, 2015
SharingCode Fix metadata file Sep 8, 2016
SoMA [ios] update min os version to 8 Jul 18, 2017
SpriteSheetDemo [SpriteSheetDemo] Update NuGet packages May 3, 2017
StandardControls fix incompatible xibs Sep 26, 2017
TablesLists fix incompatible storyboards/xibs Sep 5, 2017
Tasky Fix metadata file Sep 8, 2016
TaskyPortable Bump minimum target version to iOS 6.0 Aug 26, 2016
TaskyPro [TaskyPro] add Windows screenshot Oct 1, 2015
TestCloud Move the test cloud samples to their new repository. Jan 14, 2015
TexturedCubeES30 Fix metadata file Sep 8, 2016
TipCalc [ios] update min os version to 8 Jul 18, 2017
Touch fix incompatible storyboards/xibs Sep 5, 2017
VisualBasic [pcl] update VisualBasic readmes Jul 30, 2015
WCF-Walkthrough [WCF-Walkthrough] fix for # 40391 Jun 21, 2016
WalkingGameMG Fix metadata file Sep 8, 2016
Weather Merge pull request #51 from gonzalonm/fix_weather_app Mar 1, 2017
WebServices Bump minimum target version to iOS 6.0 Aug 26, 2016
XamarinInsights Fix metadata file Sep 8, 2016
.gitignore Update .gitignore Jul 18, 2016
README.md Update README.md Sep 8, 2016
Xamarin.Edu.SampleGallery.Core.dll Update sample validator. Jul 5, 2012
install-hook.bat Add hook installers. Nov 27, 2011
install-hook.sh Add hook installers. Nov 27, 2011
mdtool-build Fix invocation of mdtool-build. Nov 24, 2011
pre-commit.posix Fix usage of `find` in some scripts. Feb 17, 2012
pre-commit.windows Fix usage of `find` in some scripts. Feb 17, 2012
validate.posix Fix usage of `find` in some scripts. Feb 17, 2012
validate.windows Fix usage of `find` in some scripts. Feb 17, 2012
xamarin-unified-notes.rtf mobile-samples unified Dec 2, 2014
xcsv.exe Update sample validator. Jul 5, 2012

README.md

Mobile Samples

This repository contains a number of samples that show how to share code between Xamarin.iOS and Xamarin.Android.

License

The Apache License 2.0 applies to all samples in this repository.

Copyright 2011 Xamarin Inc

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Contributing

Before adding a sample to the repository, please run either install-hook.bat or install-hook.sh depending on whether you're on Windows or a POSIX system. This will install a Git hook that runs the Xamarin code sample validator before a commit, to ensure that all samples are good to go.

Samples Submission Guidelines

Galleries

We love samples! Application samples show off our platform and provide a great way for people to learn our stuff. And we even promote them as a first-class feature of the docs site. You can find our two sample galleries here:

Sample GitHub Repositories

These sample galleries are populated by samples in our six sample GitHub repos:

The mobile-samples repository is for samples that are cross-platform. The mac-ios-samples repository is for samples that are Mac/iOS only.

Sample Requirements

We welcome sample submissions. Please ping Nat or Miguel for repo commit access.

However, because the sample galleries are powered by the github sample repos, each sample needs to have the following things:

  • Screenshots - a folder called Screenshots that has at least one screen shot of the sample (preferably a screen shot for every page or every major functionality piece, people really key off these things). for the xplat samples, the folder should be split into platform folders, e.g. iOS, Android, Windows. see https://github.com/xamarin/mobile-samples/tree/master/Tasky/Screenshots for an example of this.

  • Readme - a README.md file that has the name of the sample, a description, and author attribution. sample here: https://github.com/xamarin/mobile-samples/blob/master/Tasky/README.md

  • Metadata - Finally, it needs a Metadata.xml file (https://github.com/xamarin/mobile-samples/blob/master/Tasky/Metadata.xml) that has some information:

    • ID - A GUID for the sample. You can generate this in MD under Tools menu : Insert GUID. we need this to key between articles and their associated samples

    • IsFullApplication - Boolean flag (true or false): whether or not this is a full application such as the MWC App, Tasky, etc., or it's just a feature sample, such as, how to use 'x' feature. the basic test here is, if you would submit this to the app store because it's useful, then it's a full app, otherwise it's just a feature sample.

    • Brief - Short description or what your sample does. This allows us to display a nice and clean vignette on the sample page.

    • Level - Beginner, Intermediate, or Advanced: this is the intended audience level for the sample. only the getting started samples are Beginner, as they are intended for people who are just starting with the platform. most samples are Intermediate, and a few, that dive deep into difficult APIs, should be Advanced.

    • Minimum License Requirement - Starter, Indie, Business, or Enterprise: denotes the license that a user has to have in order to build/run the sample.

    • Tags: a list of relevant tags for the app. These are:

    • Data

    • Games

    • Graphics (CoreDrawing, Animation, OpenGL...)

    • Media (Video, Sound, recording, photos)

    • Platform Features (Photo Library, Contacts, Calendars, etc.)

    • Device Features (NFC, Accelerometer, Compass, Magnemometer, Bluetooth, RFID)

    • Cloud (Web Services, Networking, etc.)

    • Backgrounding

    • Maps + Location

    • Binding + Interop (Projections)

    • Notifications

    • Touch

    • Getting Started

    • Async

    • Extension

    • SceneKit

    • FSharp

    • SupportedPlatforms: this is only for cross plat samples. It's a comma-separated list, and the valid values are iOS, Android, and Windows.

    • Gallery: This tag must contain a value of true if you want the sample to show up in the samples gallery on the developer portal.

  • Buildable Sln and CSProj file - the project must build and have the appropriate project scaffolding (solution + proj).

A good example of this stuff is here in the drawing sample: https://github.com/xamarin/monotouch-samples/tree/master/Drawing

For a x-platform sample, please see: https://github.com/xamarin/mobile-samples/tree/master/Tasky

GitHub Integration

We integrate tightly with Git to make sure we always provide working samples to our customers. This is achieved through a pre-commit hook that runs before your commit goes through, as well as a post-receive hook on GitHub's end that notifies our samples gallery server when changes go through.

To you, as a sample committer, this means that before you push to the repos, you should run the "install-hook.bat" or "install-hook.sh" (depending on whether you're on Windows or OS X/Linux, respectively). These will install the Git pre-commit hook. Now, whenever you try to make a Git commit, all samples in the repo will be validated. If any sample fails to validate, the commit is aborted; otherwise, your commit goes through and you can go ahead and push.

This strict approach is put in place to ensure that the samples we present to our customers are always in a good state, and to ensure that all samples integrate correctly with the sample gallery (README.md, Metadata.xml, etc). Note that the master branch of each sample repo is what we present to our customers for our stable releases, so they must always Just Work.

Should you wish to invoke validation of samples manually, simply run "validate.windows" or "validate.posix" (again, Windows vs OS X/Linux, respectively). These must be run from a Bash shell (i.e. a terminal on OS X/Linux or the Git Bash terminal on Windows).

If you have any questions, don't hesitate to ask!