microsoft / bikesharing360_botbuilderapps

BikeSharing360 BotBuilderApps

#BikeSharing360 During our Connect(); event this year we presented 15 demos in Scott Guthrie’s and Scott Hanselman’s keynotes. If you missed the keynotes, you can watch the recording in Channel 9.

This year, we built the technology stack for a fictional company named BikeSharing360, which allows users to rent bikes from one location to another.

BikeSharing360 is a fictitious example of a smart bike sharing system with 10,000 bikes distributed in 650 stations located throughout New York City and Seattle. Their vision is to provide a modern and personalized experience to riders and to run their business with intelligence.

In this demo scenario, we built several apps for both the enterprise and the consumer (bike riders). You can find all other BikeSharing360 repos in the following locations:

*Mobile Apps *Backend Services *Websites *Single Container Apps *Multi Container Apps *Cognitive Services Kiosk App *Azure Bot App

BikeSharing360 Azure Bot Builder Apps

BikeSharing360BotBuilder App is another implementation of the [BikeSharing360Bot] (https://github.com/Microsoft/BikeSharing360_BotApps) using bot builder framework. Besides the basic scenarios, it adds the scenario of collabrate customers and employees in the bot.

Screens

Requirements

You need an Azure subscription to deploy the bot service. Try it for free. This app works with the Azure Bot Service. You can find documentation for Azure Bot Service here.

Setup the bot service

1. Deploy CustomerServiceApis into Azure (You need a bing map service subscription to make "GetMapWithRoute" api work).
2. Deploy BikeSharing360BotBuilderApp into Azure.
3. Go to https://www.luis.ai and log in with your live account.
4. Click "New App"->"Import Existing Application" and choose luis\BikeSharing360Luis.json. BikeSharing360Luis will be created.
5. Enter the "BikeSharing360Luis" app. Click "train" button on the left bottom. Then click "publish" on the left. Save the app-id and subscription-key information from the URL.
6. Go to BikeSharing360_BotBuilderApp\Controllers\BikeSharing360LuisDialog.cs, replace "YourModelId", "YourSubscriptionKey" with the keys you got in step 4.
7. Go to BikeSharing360_BotBuilderApp\Controllers\Backend\Consts.cs, update "YourBackendServiceBaseUrl".
8. Submit the code.
9. Now, you can publish the bot (How) and test it.

How to sign up for Microsoft Azure

You need an Azure account to work with this demo code. You can:

• Open an Azure account for free Azure subscription. You get credits that can be used to try out paid Azure services. Even after the credits are used up, you can keep the account and use free Azure services and features, such as the Web Apps feature in Azure App Service.
• Activate Visual Studio subscriber benefits. Your Visual Studio subscription gives you credits every month that you can use for paid Azure services.
• Not a Visual Studio subscriber? Get a $25 monthly Azure credit by joining Visual Studio Dev Essentials.

Blogs posts

Here's links to blog posts related to this project:

• Xamarin Blog: Microsoft Connect(); 2016 Recap
• The Visual Studio Blog: Announcing the new Visual Studio for Mac
• The Visual Studio Blog: Introducing Visual Studio Mobile Center (Preview)
• The Visual Studio Blog: Visual Studio 2017 Release Candidate

Copyright and license

• Code and documentation copyright 2016 Microsoft Corp. Code released under the MIT license.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

bikesharing360_botbuilderapps's Issues

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request