Visual Studio Code offers a completely focused and distraction free view using Zen Mode.
This mode eliminates all the UI abstraction from the code editor, and you can only have the current working file as focused. As a developer this is extremely helpful when working on a single code file.
You can turn On/Off the Zen Mode from the View > Appearance
Focused (Zen) View in Visual Studio Code
You can activate the Zen Mode from View > Appearance and by selecting “Zen Mode” or just by using the shortcut key Ctrl+KZ
This can also be enabled using command pallet by executing a command: “View: Toggle Zen Mode“
This will remove all the UI element except the current working window in Visual Studio Code.
Customizing the Focused View – Zen Mode
You can also customize the Focused view – Zen Mode by Opening the Settings Dialog from the Setting Option in VS Code or using Ctrl+,
Zen Mode settings windows provide several customization option including
Hide Activity Bar
Line Number Hide
Hide Status Bar
All these settings are turned on by default. You can turn them off and bring some of the control back in the UI Elements.
“Restore” option keeping it enable is always recommended, as if you open any new windows during Zen Mode, it will bring that back by presenting the Zen Mode. Following image shows the quick example of “Hide Status Bar” turned off view.
To summarize, this is a great feature when you really want to work in a completely distraction free IDE.
If you like this article, share it with your friends and collegues,
For emails I expect a quick response to, I’ll use 3 days
Unless that’s a weekend, I use Monday
Some things I’ll use a week, or 2 weeks – it just depends how much work the person needs to do to be able to reply to me
But sometimes I just use it for myself. I go on holidays soon and there are some things I can’t do until I get back, so I have a bunch of reminders scheduled to bounce back to resume email threads when I return
This can be used by professionals who go with clients and need to followup if emails from the client.
Microsoft is working on the new “One Outlook” which will offer functionality that is identical to the all supported platforms, like windows, mac and office 365 subscriptions based version.
The application will be based on the Outlook web application that users may access in modern web browsers. Microsoft plans to replace all existing Outlook desktop programs and apps with the new version; this includes Win32 versions of Outlook, Outlook for Mac, and the Mail and Calendar applications that are exclusive Windows 10 applications.
Windows 10 users who use the Mail or Calendar application will be replaced by One Outlook eventually. Microsoft plans to put them into maintenance mode, and the last update for these clients will be a user interface update this year.
A website and setup for Windows is already available; the current version does not replicate all functionality of the desktop applications or web app of Outlook. It lacks many features including a full offline experience, and the setup program is not even signed yet. Check out the download links in WalkingCat’s tweet if you are interested in downloading the files.
SharePoint supports three types of authentication policies:
Add-In Policy – We are using this policy to authenticate the external system to access SharePoint
User +Add-In Policy
We require the following information in various requests to authenticate with SharePoint online site.
Realm (Tenant Id)
Authorize Postman to access SharePoint
We need to authorize postman to access SharePoint resources using REST API endpoints.
To do that we will need to pass access token values as a request header.
To get the access-token, we should generate Client Id and Secret information from the site by registering as an App only Add-In in SharePoint site. This is the same as registering an add-in for Provider Hosted Add-In.
I have provided the steps below to get the Tenant Id, Access Token, and data from SharePoint using Postman utility.
Navigate and login to SharePoint online site.
Then navigate to the Register Add-In page by entering the URL as
In the App Information section, click the Generate button next to the Client Id and Client Secret textboxes to generate the respective values.
Enter Add-In Title in Title textbox
Enter AppDomian as a localhost
Enter RedirectUri as a https://localhost
Click Create button, which registers the add-in and returns the success message with created information.
Save this information safely, we will need that in the following step.
Grant Permissions to Add-In
Once the Add-In is registered, we need to set the permissions for that add-in to access the SharePoint data. We will set the Read permission level to the web scope so that we will be able to read the web information.
Navigate to the SharePoint site
Then enter the URL https://<sitename>.sharepoint.com/_layouts/15/appinv.aspx in the browser. This will redirect to the Grant permission page.
Enter the Client ID(which we have generated earlier), in the AppId textbox and click the Lookup button. That will populate the value to other text boxes in Title, App Domain, and Redirect Url
Now, enter the below xml in the Permission Request.
Click Create button. This will redirect to you page, where we have to trust the add-in to read items from website.
Note: If we want to access site collection or tenant level, we have to add the XML accordingly
Retrieve the Tenant ID
Once we registered the Client Id and Secret with the permissions, we are ready to access the SharePoint information from external system or tools.
At first, we have to know the Tenant ID. Follow the below steps to obtain that information from the postman. Postman helps to get the tenant Id by requesting the below URL with an Authorization header
Launch Postman chrome extension
Select the Get Method
Enter the below URL in the “Request URL” textbox https://<sitename>/sharepoint.com/_vti_bin/client.svc/
Configure the below information in the header section to send along with the URL request method = Get
We are interested in two values, realm and client_id from the above response.
Generate the Access Token
In response header, we will get WWW-Authenticate as one of the header and that contains the necessary information required for next step. The realm value contains the tenant id for the SharePoint Online site and clientid value contains the resource information (we’ll use it later).
After getting the Tenant ID, we have to form a URL with the below format https://accounts.accesscontrol.windows.net/<TenantID>/tokens/OAuth/2 for requesting the access token.
Apply the below configurations in header Method = POST
After applying the configuration, click Send button. That will returns the response with the Access Token.
Once we are received the access token, its like we got the authorization to access the SharePoint data based on the permission applied in Grant Permission as Add-In section.
We have to pass the access token as “token_type access_token”
Access the SharePoint resource
Now we have the access token, So we can now pass this token in Authorization header with the SharePoint REST API to get the information.
In Postman tool, add the below URL to retrieve the web title