Carga inicial de codigo

Codigo de aplicacion hasta entregable del 25 de Abril, proximos releases
seran cargados posteriormente.

Author: wlnaim

PueblosMagicos/.nuget/NuGet.Config

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+  <solution>
+    <add key="disableSourceControlIntegration" value="true" />
+  </solution>
+</configuration>

PueblosMagicos/.nuget/NuGet.exe

@@ -0,0 +1,144 @@
+<?xml version="1.0" encoding="utf-8"?>
+<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+    <PropertyGroup>
+        <SolutionDir Condition="$(SolutionDir) == '' Or $(SolutionDir) == '*Undefined*'">$(MSBuildProjectDirectory)\..\</SolutionDir>
+
+        <!-- Enable the restore command to run before builds -->
+        <RestorePackages Condition="  '$(RestorePackages)' == '' ">false</RestorePackages>
+
+        <!-- Property that enables building a package from a project -->
+        <BuildPackage Condition=" '$(BuildPackage)' == '' ">false</BuildPackage>
+
+        <!-- Determines if package restore consent is required to restore packages -->
+        <RequireRestoreConsent Condition=" '$(RequireRestoreConsent)' != 'false' ">true</RequireRestoreConsent>
+
+        <!-- Download NuGet.exe if it does not already exist -->
+        <DownloadNuGetExe Condition=" '$(DownloadNuGetExe)' == '' ">false</DownloadNuGetExe>
+    </PropertyGroup>
+
+    <ItemGroup Condition=" '$(PackageSources)' == '' ">
+        <!-- Package sources used to restore packages. By default, registered sources under %APPDATA%\NuGet\NuGet.Config will be used -->
+        <!-- The official NuGet package source (https://www.nuget.org/api/v2/) will be excluded if package sources are specified and it does not appear in the list -->
+        <!--
+            <PackageSource Include="https://www.nuget.org/api/v2/" />
+            <PackageSource Include="https://my-nuget-source/nuget/" />
+        -->
+    </ItemGroup>
+
+    <PropertyGroup Condition=" '$(OS)' == 'Windows_NT'">
+        <!-- Windows specific commands -->
+        <NuGetToolsPath>$([System.IO.Path]::Combine($(SolutionDir), ".nuget"))</NuGetToolsPath>
+    </PropertyGroup>
+
+    <PropertyGroup Condition=" '$(OS)' != 'Windows_NT'">
+        <!-- We need to launch nuget.exe with the mono command if we're not on windows -->
+        <NuGetToolsPath>$(SolutionDir).nuget</NuGetToolsPath>
+    </PropertyGroup>
+
+    <PropertyGroup>
+        <PackagesProjectConfig Condition=" '$(OS)' == 'Windows_NT'">$(MSBuildProjectDirectory)\packages.$(MSBuildProjectName.Replace(' ', '_')).config</PackagesProjectConfig>
+        <PackagesProjectConfig Condition=" '$(OS)' != 'Windows_NT'">$(MSBuildProjectDirectory)\packages.$(MSBuildProjectName).config</PackagesProjectConfig>
+    </PropertyGroup>
+
+    <PropertyGroup>
+      <PackagesConfig Condition="Exists('$(MSBuildProjectDirectory)\packages.config')">$(MSBuildProjectDirectory)\packages.config</PackagesConfig>
+      <PackagesConfig Condition="Exists('$(PackagesProjectConfig)')">$(PackagesProjectConfig)</PackagesConfig>
+    </PropertyGroup>
+    
+    <PropertyGroup>
+        <!-- NuGet command -->
+        <NuGetExePath Condition=" '$(NuGetExePath)' == '' ">$(NuGetToolsPath)\NuGet.exe</NuGetExePath>
+        <PackageSources Condition=" $(PackageSources) == '' ">@(PackageSource)</PackageSources>
+
+        <NuGetCommand Condition=" '$(OS)' == 'Windows_NT'">"$(NuGetExePath)"</NuGetCommand>
+        <NuGetCommand Condition=" '$(OS)' != 'Windows_NT' ">mono --runtime=v4.0.30319 "$(NuGetExePath)"</NuGetCommand>
+
+        <PackageOutputDir Condition="$(PackageOutputDir) == ''">$(TargetDir.Trim('\\'))</PackageOutputDir>
+
+        <RequireConsentSwitch Condition=" $(RequireRestoreConsent) == 'true' ">-RequireConsent</RequireConsentSwitch>
+        <NonInteractiveSwitch Condition=" '$(VisualStudioVersion)' != '' AND '$(OS)' == 'Windows_NT' ">-NonInteractive</NonInteractiveSwitch>
+
+        <PaddedSolutionDir Condition=" '$(OS)' == 'Windows_NT'">"$(SolutionDir) "</PaddedSolutionDir>
+        <PaddedSolutionDir Condition=" '$(OS)' != 'Windows_NT' ">"$(SolutionDir)"</PaddedSolutionDir>
+
+        <!-- Commands -->
+        <RestoreCommand>$(NuGetCommand) install "$(PackagesConfig)" -source "$(PackageSources)"  $(NonInteractiveSwitch) $(RequireConsentSwitch) -solutionDir $(PaddedSolutionDir)</RestoreCommand>
+        <BuildCommand>$(NuGetCommand) pack "$(ProjectPath)" -Properties "Configuration=$(Configuration);Platform=$(Platform)" $(NonInteractiveSwitch) -OutputDirectory "$(PackageOutputDir)" -symbols</BuildCommand>
+
+        <!-- We need to ensure packages are restored prior to assembly resolve -->
+        <BuildDependsOn Condition="$(RestorePackages) == 'true'">
+            RestorePackages;
+            $(BuildDependsOn);
+        </BuildDependsOn>
+
+        <!-- Make the build depend on restore packages -->
+        <BuildDependsOn Condition="$(BuildPackage) == 'true'">
+            $(BuildDependsOn);
+            BuildPackage;
+        </BuildDependsOn>
+    </PropertyGroup>
+
+    <Target Name="CheckPrerequisites">
+        <!-- Raise an error if we're unable to locate nuget.exe  -->
+        <Error Condition="'$(DownloadNuGetExe)' != 'true' AND !Exists('$(NuGetExePath)')" Text="Unable to locate '$(NuGetExePath)'" />
+        <!--
+        Take advantage of MsBuild's build dependency tracking to make sure that we only ever download nuget.exe once.
+        This effectively acts as a lock that makes sure that the download operation will only happen once and all
+        parallel builds will have to wait for it to complete.
+        -->
+        <MsBuild Targets="_DownloadNuGet" Projects="$(MSBuildThisFileFullPath)" Properties="Configuration=NOT_IMPORTANT;DownloadNuGetExe=$(DownloadNuGetExe)" />
+    </Target>
+
+    <Target Name="_DownloadNuGet">
+        <DownloadNuGet OutputFilename="$(NuGetExePath)" Condition=" '$(DownloadNuGetExe)' == 'true' AND !Exists('$(NuGetExePath)')" />
+    </Target>
+
+    <Target Name="RestorePackages" DependsOnTargets="CheckPrerequisites">        
+        <Exec Command="$(RestoreCommand)"
+              Condition="'$(OS)' != 'Windows_NT' And Exists('$(PackagesConfig)')" />
+
+        <Exec Command="$(RestoreCommand)"
+              LogStandardErrorAsError="true"
+              Condition="'$(OS)' == 'Windows_NT' And Exists('$(PackagesConfig)')" />
+    </Target>
+
+    <Target Name="BuildPackage" DependsOnTargets="CheckPrerequisites">
+        <Exec Command="$(BuildCommand)"
+              Condition=" '$(OS)' != 'Windows_NT' " />
+
+        <Exec Command="$(BuildCommand)"
+              LogStandardErrorAsError="true"
+              Condition=" '$(OS)' == 'Windows_NT' " />
+    </Target>
+
+    <UsingTask TaskName="DownloadNuGet" TaskFactory="CodeTaskFactory" AssemblyFile="$(MSBuildToolsPath)\Microsoft.Build.Tasks.v4.0.dll">
+        <ParameterGroup>
+            <OutputFilename ParameterType="System.String" Required="true" />
+        </ParameterGroup>
+        <Task>
+            <Reference Include="System.Core" />
+            <Using Namespace="System" />
+            <Using Namespace="System.IO" />
+            <Using Namespace="System.Net" />
+            <Using Namespace="Microsoft.Build.Framework" />
+            <Using Namespace="Microsoft.Build.Utilities" />
+            <Code Type="Fragment" Language="cs">
+                <![CDATA[
+                try {
+                    OutputFilename = Path.GetFullPath(OutputFilename);
+
+                    Log.LogMessage("Downloading latest version of NuGet.exe...");
+                    WebClient webClient = new WebClient();
+                    webClient.DownloadFile("https://www.nuget.org/nuget.exe", OutputFilename);
+
+                    return true;
+                }
+                catch (Exception ex) {
+                    Log.LogErrorFromException(ex);
+                    return false;
+                }
+            ]]>
+            </Code>
+        </Task>
+    </UsingTask>
+</Project>

PueblosMagicos/.nuget/NuGet.targets

@@ -0,0 +1 @@
+{"Name":"Google Play Services - Location","Id":3336,"Alias":"googleplayservices-location","Description":"Google Play Services - Location\n===============================\n\nOne of the unique features of mobile applications is location awareness. Mobile users take their devices with them everywhere, and adding location awareness to your app offers users a more contextual experience. The location APIs available in Google Play services facilitate adding location awareness to your app with automated location tracking, geofencing, and activity recognition.\n\n\n\n\n\nGoogle Play Services\n====================\n\nGive your apps more features to attract users on a wider range of devices. With Google Play services, your app can take advantage of the latest, Google-powered features such as Maps, Google+, and more, with automatic platform updates distributed as an APK through the Google Play store. This makes it faster for your users to receive updates and easier for you to integrate the newest that Google has to offer.\n\n\nDevelop\n-------\n\nShip higher quality apps. Faster.\nGet a headstart on your development with Google services that you can use out-of-the-box.\n - Analytics\n - Sign in with Google\n - Maps\n - Places\n - Engage\n\n\n\nGrow an active user base\n------------------------\n\nReach new users and find ways to keep them coming back to your app.\n - Google Cloud Messaging\n - App Indexing\n - App Install Ads\n - App Invites\n - Earn\n\n\n\nTap into a range of tools to make more money\n--------------------------------------------\n\nTake a user-by-user approach to monetization that maximizes your app revenue.\n - AdMob\n - In-App Billing and Subscriptions\n - Android Pay\n \n\n\nMore ways to enhance your app\n-----------------------------\n\n### Use location to power context\n\nRespond to where users are and what they\u0027re doing. Enrich your app with high-accuracy location reporting, geofencing, and activity recognition.\n\n### Stream content to TVs and speakers\nLet users send audio and visual content to any Cast-enabled TV or speaker and control it from their phones or tablets.\n\n### Add social features to your games\nEnhance your games and learn more about your players. Add achievements, leaderboards, saved games, real-time multiplayer, and more.\n\n### Enhance your app for fitness\nParticipate in the fitness ecosystem and add high-engagement features to your app. Analyze raw sensor data or take advantage of shared fitness data.\n\n### Store and manage files in the cloud\nLet users interact with nearly any aspect of their Google Drive content, including sharing permissions, file revisions, and connected apps.\n\n### Support voice actions\nLet users engage with your app quickly and conveniently through voice commands. Respond to system actions or add custom actions of your own.\n\n","Version":"42.1001.0.0","Summary":"Add location awareness to your app with automated location tracking, geofencing, and activity recognition.","QuickStart":"One of the unique features of mobile applications is location awareness. Mobile users take their devices with them everywhere, and adding location awareness to your app offers users a more contextual experience. The location APIs available in Google Play services facilitate adding location awareness to your app with automated location tracking, geofencing, and activity recognition.\n\n\n\nRequired Android API Levels\n===========================\n\nWe recommend setting your app\u0027s *Target Framework* and *Target Android version* to **Android 5.0 (API Level 21)** or higher in your app project settings.\n\nThis Google Play Service SDK\u0027s requires a *Target Framework* of at least Android 4.1 (API Level 16) to compile.\n\nYou may still set a lower *Minimum Android version* (as low as Android 2.3 - API Level 9) so your app will run on older versions of Android, however you must ensure you do not use any API\u0027s at runtime that are not available on the version of Android your app is running on.\n\n\n\n\nAndroid Manifest \n================\n\nSome Google Play Services APIs require specific metadata, attributes, permissions or features to be declared in your *AndroidManifest.xml* file.\n\nThese can be added manually to the *AndroidManifest.xml* file, or merged in through the use of assembly level attributes.\n\n\nThe SDK requires the *CourseLocation* or *FineLocation* permission(s) to work correctly.  If you specify *CourseLocation* location accuracy will be lower than if you choose *FineLocation*.  Pick the appropriate one for your application.  You can have these automatically added to your *AndroidManifest.xml* file by including the following assembly level attributes:\n\n```csharp\n[assembly: UsesPermission (Android.Manifest.Permission.FineLocation)]\n// Or\n[assembly: UsesPermission (Android.Manifest.Permission.CourseLocation)]\n```\n\n\n\nSamples\n=======\n\nYou can find a Sample Application within each Google Play Services component.  The sample will demonstrate the necessary configuration and some basic API usages.\n\n\n\n\n\n\nLearn More\n==========\n\nYou can learn more about the various Google Play Services SDKs \u0026 APIs by visiting the official [Google APIs for Android][3] documentation\n\n\nYou can learn more about Google Play Services Location by visiting the official [Location](https://developer.android.com/training/location/index.html) documentation.\n\n\n\n[1]: https://console.developers.google.com/ \"Google Developers Console\"\n[2]: https://developer.xamarin.com/guides/android/deployment,_testing,_and_metrics/MD5_SHA1/ \"Finding your SHA-1 Fingerprints\"\n[3]: https://developers.google.com/android/ \"Google APIs for Android\"\n[4]: https://firebase.google.com/console/ \"Firebase Developer Console\"\n[5]: https://firebase.google.com/ \"Firebase\"\n","Hash":"a9c7034ecd775c5a9444209140113fe9","TargetPlatforms":["android"],"TrialHash":null}

PueblosMagicos/Components/googleplayservices-location-42.1001.0.0.info

@@ -0,0 +1,72 @@
+Google Play Services - Location
+===============================
+
+One of the unique features of mobile applications is location awareness. Mobile users take their devices with them everywhere, and adding location awareness to your app offers users a more contextual experience. The location APIs available in Google Play services facilitate adding location awareness to your app with automated location tracking, geofencing, and activity recognition.
+
+
+
+
+
+Google Play Services
+====================
+
+Give your apps more features to attract users on a wider range of devices. With Google Play services, your app can take advantage of the latest, Google-powered features such as Maps, Google+, and more, with automatic platform updates distributed as an APK through the Google Play store. This makes it faster for your users to receive updates and easier for you to integrate the newest that Google has to offer.
+
+
+Develop
+-------
+
+Ship higher quality apps. Faster.
+Get a headstart on your development with Google services that you can use out-of-the-box.
+ - Analytics
+ - Sign in with Google
+ - Maps
+ - Places
+ - Engage
+
+
+
+Grow an active user base
+------------------------
+
+Reach new users and find ways to keep them coming back to your app.
+ - Google Cloud Messaging
+ - App Indexing
+ - App Install Ads
+ - App Invites
+ - Earn
+
+
+
+Tap into a range of tools to make more money
+--------------------------------------------
+
+Take a user-by-user approach to monetization that maximizes your app revenue.
+ - AdMob
+ - In-App Billing and Subscriptions
+ - Android Pay
+ 
+
+
+More ways to enhance your app
+-----------------------------
+
+### Use location to power context
+
+Respond to where users are and what they're doing. Enrich your app with high-accuracy location reporting, geofencing, and activity recognition.
+
+### Stream content to TVs and speakers
+Let users send audio and visual content to any Cast-enabled TV or speaker and control it from their phones or tablets.
+
+### Add social features to your games
+Enhance your games and learn more about your players. Add achievements, leaderboards, saved games, real-time multiplayer, and more.
+
+### Enhance your app for fitness
+Participate in the fitness ecosystem and add high-engagement features to your app. Analyze raw sensor data or take advantage of shared fitness data.
+
+### Store and manage files in the cloud
+Let users interact with nearly any aspect of their Google Drive content, including sharing permissions, file revisions, and connected apps.
+
+### Support voice actions
+Let users engage with your app quickly and conveniently through voice commands. Respond to system actions or add custom actions of your own.
+

PueblosMagicos/Components/googleplayservices-location-42.1001.0.0.png

@@ -0,0 +1,59 @@
+One of the unique features of mobile applications is location awareness. Mobile users take their devices with them everywhere, and adding location awareness to your app offers users a more contextual experience. The location APIs available in Google Play services facilitate adding location awareness to your app with automated location tracking, geofencing, and activity recognition.
+
+
+
+Required Android API Levels
+===========================
+
+We recommend setting your app's *Target Framework* and *Target Android version* to **Android 5.0 (API Level 21)** or higher in your app project settings.
+
+This Google Play Service SDK's requires a *Target Framework* of at least Android 4.1 (API Level 16) to compile.
+
+You may still set a lower *Minimum Android version* (as low as Android 2.3 - API Level 9) so your app will run on older versions of Android, however you must ensure you do not use any API's at runtime that are not available on the version of Android your app is running on.
+
+
+
+
+Android Manifest 
+================
+
+Some Google Play Services APIs require specific metadata, attributes, permissions or features to be declared in your *AndroidManifest.xml* file.
+
+These can be added manually to the *AndroidManifest.xml* file, or merged in through the use of assembly level attributes.
+
+
+The SDK requires the *CourseLocation* or *FineLocation* permission(s) to work correctly.  If you specify *CourseLocation* location accuracy will be lower than if you choose *FineLocation*.  Pick the appropriate one for your application.  You can have these automatically added to your *AndroidManifest.xml* file by including the following assembly level attributes:
+
+```csharp
+[assembly: UsesPermission (Android.Manifest.Permission.FineLocation)]
+// Or
+[assembly: UsesPermission (Android.Manifest.Permission.CourseLocation)]
+```
+
+
+
+Samples
+=======
+
+You can find a Sample Application within each Google Play Services component.  The sample will demonstrate the necessary configuration and some basic API usages.
+
+
+
+
+
+
+Learn More
+==========
+
+You can learn more about the various Google Play Services SDKs & APIs by visiting the official [Google APIs for Android][3] documentation
+
+
+You can learn more about Google Play Services Location by visiting the official [Location](https://developer.android.com/training/location/index.html) documentation.
+
+
+
+[1]: https://console.developers.google.com/ "Google Developers Console"
+[2]: https://developer.xamarin.com/guides/android/deployment,_testing,_and_metrics/MD5_SHA1/ "Finding your SHA-1 Fingerprints"
+[3]: https://developers.google.com/android/ "Google APIs for Android"
+[4]: https://firebase.google.com/console/ "Firebase Developer Console"
+[5]: https://firebase.google.com/ "Firebase"