The Maps App for .NET shows how a suite of applications can be built around the ArcGIS Platform using the ArcGIS Runtime SDK for .NET and a combination of WPF and the cross-platform framework Xamarin Forms. It demonstrates best practices around some simple but key functionality of the ArcGIS Runtime. You can use the Maps App as is, or extend it to meet your specific needs. Detailed documentation about the app and its architecture can be found on the developers website.

• Features
• Detailed Documentation
• Get Started
  • Fork the repo
  • Clone the repo
    • Command line Git
    • Configuring a Remote for a Fork
  • Configure the app
• Requirements
• Resources
• Issues
• Contributing
• MDTOC
• Licensing

• Place Search
• Geocode addresses
• Reverse Geocode
• Turn-by-turn Directions
• Dynamically switch basemaps
• Open Web Maps
• Work with ArcGIS Online or an on-premise ArcGIS Portal
• OAuth2 authentication

Read the docs for a detailed explanation of the application, including its architecture and how it leverages the ArcGIS platform, as well as how you can begin using the app right away.

This Maps App repo is a Visual Studio 2017 Project that can be directly cloned and imported into Visual Studio 2017 or higher.

Fork the Maps App repo

Once you have forked the repo, you can make a clone

Clone the Maps App cd into the maps-app-dotnet folder Make your changes and create a pull request

If you make changes in the fork and would like to sync those changes with the upstream repository, you must first configure the remote. This will be required when you have created local branches and would like to make a pull request to your upstream branch.

1. In the Terminal (for Mac users) or command prompt (fow Windows and Linux users) type git remote -v to list the current configured remote repo for your fork.
2. git remote add upstream https://github.com/Esri/maps-app-dotnet.git to specify new remote upstream repository that will be synced with the fork. You can type git remote -v to verify the new upstream.

If there are changes made in the Original repository, you can sync the fork to keep it updated with upstream repository.

1. In the terminal, change the current working directory to your local project
2. Type git fetch upstream to fetch the commits from the upstream repository
3. git checkout master to checkout your fork's local master branch.
4. git merge upstream/master to sync your local master' branch with upstream/master. Note: Your local changes will be retained and your fork's master branch will be in sync with the upstream repository.

Maps app uses authenticated ArcGIS Online services for routing and geocoding. You need to configure the app for OAuth authentication.

1. Log in to developers.arcgis.com.
2. Create a new application.
3. After creating the application, navigate to the 'Authentication' tab and add a redirect URI. Any URI should work, but try to choose something unique to your app, like my-maps-app://auth. The default value in the app's code is https://developers.arcgis.com, so you can use that as an interim value while evaluating the app.
4. While on the 'Authentication' tab, note the Client ID and the Redirect URI you specified.
5. In Helpers\Configuration.cs within the MapsApp.Shared project, replace the default client ID and Redirect URI with the values noted earlier.

• Visual Studio 2017 or higher
  • Visual Studio 2019 is required if you want to use the .NET Core version of the WPF app.
• .NET Framework 4.6.1 or higher
• ArcGIS Runtime SDK for .NET 100.11 or higher

• ArcGIS Runtime SDK for .NET Developers Site
• ArcGIS Developer Blog
• twitter@ArcGISRuntime
• twitter@esri

Find a bug or want to request a new feature enhancement? Let us know by submitting an issue.

Anyone and everyone is welcome to contribute. We do accept pull requests.

1. Get involved
2. Report issues
3. Contribute code
4. Improve documentation

Generation of this and other documents' table of contents in this repository was performed using the MDTOC package for Atom.

Copyright 2019 Esri

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

https://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.

A copy of the license is available in the repository's LICENSE file.

For information about licensing your deployed app, see License your app.