Skip to main content

Posts

Showing posts from September, 2017

Technical dive into the Mobile Platform in Update 10

With the recent Platform update 10 they introduced server side coding and made some enhancements to the mobile platform. This brings a lot of flexibility and capabilities. Below I will focus on just the Expense Management Mobile workspace. For one, the Mobile workspaces are now embedded in the AOT as a resource file. Notice how it says “In metadata”. This indicates that it has loaded from the AOT. I think this is a good move. Its all about ALM. This is also great to keep the server side and client side in sync. The nice thing is that the Expense Mobile solution is in its own model. Makes it easy for us to track and learn from. The main entry is the workspace resource file xml. Notice the guid, this is important for doing some server side coding. Now lets take a look at the workspace class. You will notice the same guid is used for the class attribute. in one of my prior posts, I mentioned that the currency field wasn’t being defaulted when entering a new expense. Now with server side c

Azure AD Authentication for Windows Applications

In this post I will describe how you can get the login dialog to pop up when you are developing a windows desktop application. Below is an example of the dialog appearing. Below is a sample code how to acquire the token. string authorityUri = "https://login.windows.net/common/oauth2/authorize"; Uri redirectURI = new Uri("https://login.live.com/oauth20_desktop.srf"); AuthenticationContext authenticationContext = new AuthenticationContext(authorityUri); AuthenticationResult authenticationResult = authenticationContext.AcquireTokenAsync( ClientConfig.Default.ActiveDirectoryResource, ClientConfig.Default.ActiveDirectoryClientAppId, redirectURI, new PlatformParameters(PromptBehavior.RefreshSession)).Result; Add the redirect URI for https://login.live.com/oauth20_desktop.srf Reference: https://docs.microsoft.com/en-us/rest/api/datacatalog/authenticate-a-client-app