I have created a profile for the O365 CLI.
It was as easy as one and one equals two. So with all the goodness of the O365 CLI and the option to create custom profiles.
This provides consistency, something I like, and provides support for programming ligatures. I use the Fire Code font in both Visual Studio Code as well as all my terminals. I agree with most of the points in his post except that I use a different font. Windows Terminal ProfilesĪs described in the post by Scott you can create profiles and apply certain settings. And with some additional settings described by Scott Hanselman in how to make a pretty prompt in Windows Terminal, you can make it look awesome. Now with the Windows Terminal that has become even easier.
The fact that you can work with tabs to fire up new instances is something I loved since I used cmder. I love the concept of an integrated terminal, and it looks beautiful. Windows TerminalĪnd as a Geek I do want to play around with new stuff. I even have some scripts that prep some of the demos I do during events. As well as reading and settings certain settings for demos. The main commands I use are for cleaning up some of the things I do on my tenant. I assume that is how most people are using it. In addition to that, it also is used in some of my build pipelines. I use the O365 CLI mainly for managing my dev tenant. But I am still on windows, so when I recently formatted my laptop I reconsidered installing the CLI again. And I must admit I like the tool to manage my Office 365 dev tenant. Using the Office 365 CLI, you can manage your Microsoft Office 365 tenant and SharePoint Framework projects on any platform.
0 kommentar(er)
