Rakesh Vemula Blog https://docs.microsoft.com/archive/blogs/vemula/feed.xml Drive towards unknown Wed, 17 Apr 2019 03:43:04 GMT en-US hourly 1 Using Graph API version 2 https://docs.microsoft.com/archive/blogs/vemula/using-graph-api-version-2 Sun, 11 Mar 2018 18:48:38 GMT https://blogs.msdn.microsoft.com/vemula/?p=215
  • You don't need an azure account for registering your app.
  • With one API interface you can login using office (outlook/live) and work accounts
  • You can control your app/ user permissions directly from your app
    • Please follow the below process to register your apps.

    App Registration

    The Graph API changed its authentication protocol for supporting Microsoft and work accounts in a single API call. −      Create a new app in the below link https://apps.dev.microsoft.com/?referrer=https%3a%2f%2fdeveloper.microsoft.com%2fen-us%2fgraph%2fgraph-explorer#/appList  −      Add redirect Url from new platform, please select the “Allow Implicit Flow” while creating new platform . −       Choose appropriate permission required by your app to communicate with AD tenant. −      Generate New Password and copy it because it won’t be visible again. −      ***Your Application Id will be the client Id and password will be the client secret for all the graph/ AD communications −      Save the changes. −      We should send the admin consent for approving the app permissions to your AD tenant, AD tenant admin has to open the below URL for approving the app permissions. https://login.microsoftonline.com/{TenantName}/adminconsent?client_id={ApplicationId}&state=12345&redirect_uri={RedirectURI} Tenenetname example: Contoso.onmicrosoft.com Application Id : your appId Redirect Uri : it is the same redirect your of your app under platform section. Please update the above fields in the Uri before open it in browser.   For the programmers who are familiar with Graph API v1:
    1. Client Id will be the application Id
    2. Client secret will be the password
    3. Tenant will be same but you have to give the appropriate permissions to your app by sending and approving the admin consent
    Requesting & approving the permissions for your app can be done by using the below URL https://login.microsoftonline.com/{TenantName}/adminconsent?client_id={ApplicationId}&state=12345&redirect_uri={RedirectURI}]]>         Publishing Web App to Azure Via Visual Studio... https://docs.microsoft.com/archive/blogs/vemula/publishing-web-app-to-azure-via-visual-studio Fri, 25 Nov 2016 16:08:23 GMT https://blogs.msdn.microsoft.com/vemula/?p=165 Publishing Websites from Visual Studio" explains how can we deploy our web apps to different sources. In this post I would like concentrate mainly on how to deploy a web app in to azure with out any extra scripting...
    1. Go to "portal.azure.com" and sign in with your credentials. Click on ADD and browse for web app, You can also find web app in web + mobile category. publish_1
    2. After selecting web App you find the below screen then click on create publish_2
    3. After clicking on create there will new blade opening for filling the required credentials. publish_3_ink_li
    4. App name is nothing but the URL what you want to choose for your app. You can choose the available resource group or you can create one to deploy your site. After creating your web app the home page will be looking similar to the below page. publish_4
    5. Open your code in visual studio, right click on the project from solution explorer and select publish. From publish select the target profile as "Microsoft Azure Web Apps" then new pop up window open for your login credentials to sign in. After the pop up signs in then select the web APP slot and click on OK.
    6. In the connection details if you select the web deploy then visual studio automatically downloads the publish settings for your account.
    7. Select the mode in settings,
    8. In Preview you can see all the files which are going to publish. Then click on Publish.
    9. Visual studio will publish the files in to the selected slot.
    10. You can browse the URL and you can find the home page is replaced with your app.
    Thank you ...:)]]>         Viewing Macros in Excel… https://docs.microsoft.com/archive/blogs/vemula/viewing-macros-in-excel Fri, 25 Nov 2016 15:28:22 GMT https://blogs.msdn.microsoft.com/vemula/?p=86 Publishing Websites from Visual Studio... https://docs.microsoft.com/archive/blogs/vemula/publishing-websites-from-visual-studio Fri, 25 Nov 2016 11:55:40 GMT https://blogs.msdn.microsoft.com/vemula/?p=35
  • Select your application then right click on it to select publish.
  • Select the profile from the listed profiles or you can create one from custom. In the below screen shot I am created a new profile called test. publish_1
  • In the Connection step you can select the type of publish publish_2
  • Web Deploy, In this you can directly deploy your web app to your host site by entering the required fields.
  • Web Deploy Package, In this you can deploy your package to the given site by pointing it to the local folder.
  • FTP, You can deploy the site directly to the destination URL by filling up the required fields in the fields.
  • File System, When you don't know where to deploy it or, if you want to publish your code to local path and use the deploy folder then go with it. It is easy and one of the most used one by me. Selected File system from previous window. publish_2_2
  • After selecting the file system mode you should chose the target path to save the publish folder.
  • In settings you can choose which way you want to deploy the package, Is it release mode or debug mode. publish_3
  • In the last step you can see the preview of the selected profile, then click on the publish. publish_4
  • You can see the published files in the target path, you can deploy that to any server and point it by any IIS server web application.This way you can host your web apps.
    • ]]>         Everything about AZURE... https://docs.microsoft.com/archive/blogs/vemula/everything-about-azure Thu, 24 Nov 2016 23:05:18 GMT https://blogs.msdn.microsoft.com/vemula/?p=85 link to know about azure in depth or if you in need of training videos then go with the following link, this two links are having the updated information of Azure resource model portal needed for clearing the 70-533.]]> Powershell cmd to know the supported resource providers by location... https://docs.microsoft.com/archive/blogs/vemula/powershell-cmd-to-know-the-suppoerted-resource-providers-by-location Thu, 24 Nov 2016 12:04:14 GMT https://blogs.msdn.microsoft.com/vemula/?p=65 ]]> Could not load file or assembly Exception in Visual Studio https://docs.microsoft.com/archive/blogs/vemula/could-not-load-file-or-assembly-system-web-http-after-downgrading-from-vs-2015-to-2013 Wed, 23 Nov 2016 18:16:24 GMT https://blogs.msdn.microsoft.com/vemula/?p=25 Scenario : One of our project is developed in VS 2013 then deployed in two pre-prod servers. Later , one of the server API started throwing random exceptions. After reading few articles about the process of picking dll's by CLR we came to know that VS picks dll's by simple names not by their exact name and version. In our project one of the referenced dll is having a reference to system.web.http v4.0 and also has the referencing to 5.2 but still the CLR is picking the 4.0 version at run time. This issue can be seen only at runtime. Root Cause : Visual Studio picks referred dll's using their simple names but not by the exact name and version.
    1. If the project is having reference to the same dll of two different versions.
    2. If the GAC is having a different version of the dll not similar to the version referenced by project then compiler will be confused on what to choose.
    Solution : The Issue is solved after removing web.http v4.0 from Object Browser dll's list. So, we have to remove the duplicate dll's from Object Browser .  ]]>