Microsoft is rarely the first to jump on a train, but when they do jump, they make sure it is very simple for everybody to get on their wagon. And they did it again with Application Insights, a feature of Visual Studio Online that monitors the performance of web sites, web services, and mobile apps. They are perhaps not as feature-complete as early players (special thoughts to our friends and partners at Gibraltar Software), but their simplicity is stunning. Adding Application Insights to Your App Judge by yourself. You need just two simple steps to add monitoring to
your app: Install the Visual Studio extension “Application Insights Tools for Visual Studio”. Open your project and click on menu Tools / Add Application Insights. You’re done. No joke. Application Insights provides several monitors right out of the box, among which page load time and Windows performance counters. It also has a (still modest) API that allows you to push your own data. Perhaps the top use case you would like to implement is to measure the execution time of a method, and perhaps include the method arguments in the trace data. Measuring Method Execution Time Wouldn’t it be nice if you could add your own...(Read whole news on source site)
CEO Satya Nadella dropped a few possible clues about where he and Microsoft may be going during his first earnings-call outing. Here's my attempt to read between the lines.
Tony Prophet, most recently an HP Senior Vice President of Operations, is the new head of Windows Marketing.
Some endpoints in the GitHub API require authorization to access private details. For example, if you want to get all of a user's repositories, you'll need to authenticate to see private repositories. If you're building a third-party application that integrates with the GitHub API, it's poor form to ask for a user's GitHub credentials. Most users would be wary of providing that information. Fortunately, Github supports the OAuth web application flow. This allows your app to authenticate with GitHub without ever having access to a user's GitHub credentials. In this post, I'll show the basics of implementing this workflow using Octokit.NET. OAuth Web
Flow The basic worfklow of an OAuth flow is as follows. On an unauthenticated request to your site, your site redirects the user to the GitHub oauth login URL (hosted on github.com) with some information in the query string such as your application's identity and the list of scopes (permissions) your application requests. The GitHub Oauth login page then prompts the user to either accept or reject this authentication request. If the user is not already logged into GitHub.com, they'll login first. If the user clicks "Authorize application", then this page redirects back to your site with a special session code. Your site will...(Read whole news on source site)