It still works just like always so definitely feel free to keep using it (or clone it and take it further as you see fit). I won't be de-listing MSGraphPSEssentials from Powershell Gallery for now, and will also leave this repo here too. If you tried and/or enjoyed MSGraphPSEssentials, thank you very much, it was a fun side project for me. So this module is officially obsoleted by Microsoft's official offering. At the same time, the Invoke-MgGraphRequest function that comes with the official module is essentially a like-for-like replacement of MSGraphPSEssentials' New-MSGraphRequest, and then some. So twice the learning time required to take part, whereas with MSGraphPSEssentials, you only need to learn the MS Graph reference material and plug your requests into the New-MSGraphRequest function. Where they fall short in my opinion is that you need to learn the ins and outs of both MS Graph and their new modules, each having their own entirely different set of syntaxes. I suggest moving over to the official modules considering the fact they are backed and supported by Microsoft. Thanks to that, I will not be working on MSGraphPSEssentials any longer, unless some valid reason to comes up. Please share your own suggestions or recommended tools / processes in the comments below.FYI, at this point in time, Microsoft have delivered a proper set of PowerShell modules for interacting with Microsoft Graph. I hope you have found something useful in this post. I previously blogged about this at How to Edit Microsoft Documentation on GitHub. Azure docs, Microsoft Graph docs, etc.) For these I prefer submitting a pull request directly in the browser. Browser based pull requests – Some repositories that I collaborate on are very large and not well suited to sync locally (ex.When I am not at my desk I tend to use the newly released mobile app for GitHub. GitHub mobile app – I do submit and review a GitHub issues or pull requests on an infrequent basis.The integration with Azure DevOps and GitHub is good as well. Blazor and some ASP.NET Core) I use the Team Explorer functionality (now available out of the box) to sync repos. For the projects I do work in Visual Studio 2019 (ex. Visual Studio Team Explorer – In general I start most projects in VS Code these days. When I’m not directly in VS Code working on a repo I generally use GitHub Desktop. GitHub Desktop client – GitHub offers a desktop client that allows you to sync code, create branches, review commit history, and more.monitor builds, pull requests, and more) directly into VS Code. I use this for committing and pushing code to my GitHub repositories.Īzure Repos Extension for Visual Studio Code – There is an extension for VS Code that adds additional functionality (ex. Visual Studio Code (VS Code) – VS Code has integrated supported in-box for Git.I use a mix of the following tools to sync my repos and monitor issues or pull requests. MG.ProjectName, etc.) This helps at least group together similar projects. I do name my folders and projects based on topic though (ex. ASP.NET Core, Blazor, Console, etc.) but since I rarely have a large number of folders I haven’t done anything yet. SharePoint Online, Azure, Microsoft Graph, etc.) or technology (ex. Using the underscore for _DevOps and _GitHub means that those folders should be easy to find at the top of this folder structure even if I happen to inadvertently sort the folder.Īs for project folders, I’ve thought about subdividing based on topic (ex. Below that folder I then have the following: Instead I create a new folder called Projects at the root of my primary drive (i.e. I don’t use the default folder that any of the IDEs or tools below use (generally under my user profile folder such as “c:\Users\\…”). So balance everything that I share with what others such as my friend Steve Smith ( share on his Weekly Dev Tips blog and podcast.Ĭurrently I develop on Windows so folders and paths will reflect that. Sure I’ve written (or collaborated on) many samples (ex.Net Core console sample for Microsoft Graph) and proof of concepts for customers these past 10 years, but it wasn’t the primary focus of my job. I like to to tell people that “I play a developer on TV”, meaning it has been at least 10 years since I’ve written code as a consultant that was actually deployed to a production system. A peer of mine recently asked about how I manage local code (projects, solutions, Git repos, etc.) that may or may not be synced to a cloud repository (GitHub, Azure DevOps, etc.) Since I previously blogged about How I Blog – Updated 2018 and I’m a fan of re-using how many keys I have left I thought I would share my personal local development process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |