Watch videos with subtitles in your language, upload your videos, create your own subtitles! Click here to learn more on "how to Dotsub"

Connect_Connecting_To_Services_with_Visual_Studio_ENU

0 (0 Likes / 0 Dislikes)
  • Embed Video

  • Embed normal player Copy to Clipboard
  • Embed a smaller player Copy to Clipboard
  • Advanced Embedding Options
  • Embed Video With Transcription

  • Embed with transcription beside video Copy to Clipboard
  • Embed with transcription below video Copy to Clipboard
  • Embed transcript

  • Embed transcript in:
    Copy to Clipboard
  • Invite a user to Dotsub
[Connecting to Services with Visual Studio] [Steve Lasker, Program Manager, Visual Studio] Hi, I'm Stever Lasker, a program manager on the Cloud platform tools team. In this video, I'm going to talk about and demo how you can consume modern connected services with Visual Studio 2015. So what are connected services? They're simply the evolution of the same services we've been consuming for years. They provide technical services your development team may choose, such as authentication, caching, and data, and they provide business services, such as customer, workforce, and resource management the business likely chooses. The difference is the technologies are evolving at a rapid pace. While many are standardizing on variations of OData, REST, and OAuth, the implementations vary. Connecting to modern services requires several steps, depending on the service. Many services require service configuration for each app just to consume the service, such as OAuth tokens and secrets. What's the URI for the service? Which client libraries will you need? What code do I need, do I want? And any code added should be my code, not some generated code I can't touch. I like to say we're retiring MC Hammer with his Can't-Touch-This-style coding. Yeah, I said we were retiring you. Go away. Go. Go. And after you've consumed a service, if there was some magic configuration, what was done? What else do I need to do? What else do I need to know? Am I left to the World Wide Web just to find answers to the thing I just did? For our demo, I'll talk about one of our customers that uses TFS for their bug tracking. But they also use their business data in Salesforce to prioritize their bugs and features. We'll authenticate with Azure AD and Azure Storage for cache and tokens and Application Insights for site usage and performance. By using the services together, the triage team can rely on real business data to prioritize their bugs. Yeah, I see you. It's fun. We ready to do the demo now? So here's our LANDESK UI for our customer I was talking about. The UI is all set up. We just need to add the services behind it. The first service is our Salesforce service. And you might think to go to old faithful for add service reference, but you need to know the URI. The Salesforce services are REST endpoint. There's no standard metadata format for REST, so this dialog can't do anything with it. If I go to Manage NuGet, I can go find some libraries and find an STK that I can code against, but I still have to do all the configuration myself, both server and project, as well as write the code. Nestled right here between the two is Add Connected Service. Here we see a curated list of providers. Each provider knows how to configure that specific service. And if you don't find the one you want, you can go out to the gallery and look for some more, such as our friends at Datalogics were building a PDF service. We'll pick Salesforce, and the first thing we see is a unique configuration for the Salesforce-specific service. We pick the design time authentication for creating the connected app, the runtime authentication for how users will log in to Salesforce through this particular app. Because I chose Web server flow, I can choose a custom-branded login page. And then lastly , I can pick which objects I want to consume, because I don't want all 500 objects; I just want the two I need. So now, using that design time authentication, we'll go out to Salesforce and create that OAuth connected app. We'll bring the consumer key and secret into Web config. We'll add NuGet libraries for the client STK for consuming Salesforce. And we'll scaffold out just the code I need for this particular project. We don't want to generate all the code that every project needs. Then lastly, we'll open up some guidance docs for what you do next. What happened to my project? What, if anything, are required next steps? And what are the samples to get started with this? We don't want to put samples in your project because then you have to delete them as you get to know how to use this. We're now at Visual Studio Online. This is one that's a sample that I'm building that I'll drill into more details at Build. We'll launch that. We'll use our TFS handy-dandy selector to go get our team project. We'll configure the runtime authentication. And we can name how we want this to appear in our project. It'll give us next steps for documentation, added our Web config entries, and also generated a model class for us that includes the serialization attributes and display names so I get nice, clean property names. Now, the next step, I want to lock down my site to only LANDESK employees. I don't want to have to create yet another SQL database that I have to track where all these users are. I want to actually use AD that my company is set up for, and I'll lock down my app that way. So what we're doing here is going out to AD, configuring an AD app That's how we manage permissions to various resources. We'll take that consumer key and secret and put it in Web config. We'll scaffold out the code into the project for securing the app, providing a sign in and sign out method. And we'll give you guidance docs for where to go from here. Lastly, I want to be able to see how my site is being used. What are the performance of the site? So I'm going to use Application Insights, and I'll add this as well. Now, we'll do the NuGet and config entries like we've been doing on the other providers, but what we can do with App Insights is put a place for our telemetry to go. We're going to log all this telemetry in the app, but it needs a place to go, and I don't want to have to go set that up as well, so here the App Insights connected service provider will create a component in your Visual Studio Online portal to track your telemetry and give you real-time visibility to it. So we've added a bunch of services. That was the hard part. Now we're just left with the fun part—to write code. That's easy. And if we have any questions, we have our getting started docs right here for picking up where we left off. [aka.ms/ConnectedServices] [blogs.msdn.com/SteverLasker] [Twitter: SteverLasker] That was a quick tour of what we have coming with Visual Studio 2015. You can find more information on Connected Services here, including info on the STK for building your own connected service. I look forward to hearing from you and possibly seeing you at Build or Ignite.

Video Details

Duration: 7 minutes and 12 seconds
Country: United States
Language: English
License: All rights reserved
Genre: None
Views: 42
Posted by: duncanma on May 13, 2015

----- (Please provide translations for these languages: Chinese (Simplified) (chi_hans), Chinese (Traditional) (chi_hant), Czech (cze), English (eng), French (France) (fre_fr), German (ger), Italian (ita), Japanese (jpn), Korean (kor), Polish (pol), Portuguese (Brazil) (por_br), Russian (rus), Spanish (spa), Turkish (tur).)

Caption and Translate

    Sign In/Register for Dotsub to translate this video.