@horzsolt2006:My bad for not adding more documentation there. You need to setup your own LUIS model (and import the LUIS model that it's in there), then setup the LUIS keys in the web service. You need to deploy the web service and register it in bot framework, then apply the keys to that web.config. You need to enable direct line, get the keys and use them in the client. You also need to enable a Bing Speech API subscription and use those keys on the client as well. Without those keys, it won't work.
Hi there. At this point these APIs are in preview. So they are "free" in the sense that you can get an API key at no cost and make calls (there's a quota of how many calls / time window that you can make). At some point in the future these will go GA and then I'd expect details about the pricing model to be available.
guillaumeo, can you elaborate on what the scenario is? Do you want to hardcode a username/password in your service or have some UI that authenticates the user to call this service?
But if you have a web UI that authenticates the user and then calls this service I'd suggest making it into a REST/Web API simply because it will make your life so much easier. I might be able to provide more help once I learn more about what you are trying to build there.
Craig, drop me an e-mail on mat.velloso@microsoft.com and lets discuss this further. First thing I need to understand is what kind of app is this. You mentioned this is not an MVC app. I assume it's still ASP.Net so is this a Web Forms app? Visual Studio can add all authentication out of the box for you so the only code you will need to add is the calls to O365 which should be just a few lines of code still.
The newest tools for Visual Studio don't generate that sample snippet anymore. They felt it would be wiser to instead create a nice sample app and point people to it: https://github.com/OfficeDev/Office-365-APIs-Starter-Project-for-ASPNETMVC">https://github.com/OfficeDev/Office-365-APIs-Starter-Project-for-ASPNETMVC There are several samples over that site: https://github.com/OfficeDev/
There's not really a sample because everything there is generated out of Visual Studio. Once you install the O365 API tool for Visual Studio, everything should work. Let me know if that doesn't do the trick for some reason.
1-This is really up to the application. But yes, you could go that far. There's a great book that discusses exactly that scenario in details named "Building Hypermedia APIs with HTML5 and Node". I'd suggest taking a look at that.
I'll get a post with the remaining sample code done to cover the remaining missing bits but I know the folks on Azure are also building a sample. Either way I'll let you know.
Comments
Meet the presenter bot, a bot that presents about bots
@horzsolt2006:My bad for not adding more documentation there. You need to setup your own LUIS model (and import the LUIS model that it's in there), then setup the LUIS keys in the web service. You need to deploy the web service and register it in bot framework, then apply the keys to that web.config. You need to enable direct line, get the keys and use them in the client. You also need to enable a Bing Speech API subscription and use those keys on the client as well. Without those keys, it won't work.
TWC9: Visual Studio 2015 Launch is a Go!
I only watch this show because of the Cortana Kid.
TWC9: Windows 10 Launch, Build 10240 (is 10), Cortana Analytics Suite, Glimpse and more...
Thanks guys. I love you too <3
Episode 179: Oxford APIs with Mat Velloso
Hi there. At this point these APIs are in preview. So they are "free" in the sense that you can get an API key at no cost and make calls (there's a quota of how many calls / time window that you can make). At some point in the future these will go GA and then I'd expect details about the pricing model to be available.
Identity 201: Cloud Identity for Developers
From 05:35 onwards it's PowerPoint only. The first part is mostly Blender.
Azure, Office 365, and SharePoint Online has REST endpoints with Mat Velloso
Sometimes explaining things in the simplest possible terms helps :) But I agree there's a lot more there we didn't cover. Thanks!
Assembling Azure, Office 365, and Web Services into a real app
guillaumeo, can you elaborate on what the scenario is? Do you want to hardcode a username/password in your service or have some UI that authenticates the user to call this service?
For hardcoded username/passwords you can use ADAL's headless authentication (http://www.cloudidentity.com/blog/2014/07/08/using-adal-net-to-authenticate-users-via-usernamepassword/).
But if you have a web UI that authenticates the user and then calls this service I'd suggest making it into a REST/Web API simply because it will make your life so much easier. I might be able to provide more help once I learn more about what you are trying to build there.
Mat
Assembling Azure, Office 365, and Web Services into a real app
Craig, drop me an e-mail on mat.velloso@microsoft.com and lets discuss this further. First thing I need to understand is what kind of app is this. You mentioned this is not an MVC app. I assume it's still ASP.Net so is this a Web Forms app? Visual Studio can add all authentication out of the box for you so the only code you will need to add is the calls to O365 which should be just a few lines of code still.
Assembling Azure, Office 365, and Web Services into a real app
Craig, I just spoke with the team:
The newest tools for Visual Studio don't generate that sample snippet anymore. They felt it would be wiser to instead create a nice sample app and point people to it: https://github.com/OfficeDev/Office-365-APIs-Starter-Project-for-ASPNETMVC">https://github.com/OfficeDev/Office-365-APIs-Starter-Project-for-ASPNETMVC There are several samples over that site: https://github.com/OfficeDev/
Assembling Azure, Office 365, and Web Services into a real app
There's not really a sample because everything there is generated out of Visual Studio. Once you install the O365 API tool for Visual Studio, everything should work. Let me know if that doesn't do the trick for some reason.
HATEOAS, REST, and Hypermedia Primer with Mat Velloso
Hi Daniel:
1-This is really up to the application. But yes, you could go that far. There's a great book that discusses exactly that scenario in details named "Building Hypermedia APIs with HTML5 and Node". I'd suggest taking a look at that.
2-ASP.Net Web API allows for that and it is not uncommon. In many cases you don't want to expose directly your database objects. You can use libraries such as AutoMapper to do that, more or less like discussed here: http://stackoverflow.com/questions/14484692/web-api-queryable-how-to-apply-automapper
Feel free to ping me on @matvelloso
Mat
Azure Mobile Services, AAD and O365: Authentication and identity across services
Rob, the how to for getting authentication to work on iOS and Android are here:
http://www.matvelloso.com/2014/07/01/adal-bindings-xamarin-ios-applications-ultimate-guide/
http://www.matvelloso.com/2014/07/02/adal-bindings-xamarin-android-applications-ultimate-guide/
I'll get a post with the remaining sample code done to cover the remaining missing bits but I know the folks on Azure are also building a sample. Either way I'll let you know.