@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.
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 email@example.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.
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.