These ideas aren’t strictly to do with VS Code, but tweaking PowerShell and Git to make them more efficient for you. It’s nice to also be able to do all that from within VS Code. I use PowerShell a lot during the day to manage containers (with the navcontainerhelper module), manage Git and various tasks with our own module to call the with Azure DevOps REST API. I like a dark theme but didn’t quite get on with the one that comes with VS Code. Because we can! Having suffered for years with an IDE that didn’t even highlight keywords I took my time trying out different themes.
“how did this line of code get here”, file history, compare revisions, open the file in Azure DevOps Including the object type when the files are already in subfolders by object type and including objects IDs when we all agree we want to get rid of them and don’t care what they are as long as they’re unique seems pretty redundant to me…but I digress CRS AL Language Extensions – for renaming AL files to follow best practices and because I don’t like the convention.Azure Pipelines – intellisense for YAML build definitions.Azure Account – provides some sign in magic required by other extensions.AL Language – every so often I need an upcoming version or a NAV 2018 version but most of the time I’ve got the one from the marketplace installed.Right now I’ve got these extensions installed: (For those of us that make apps for a living it’s a sobering thought that our prospective users are likely to be the same). If I don’t use it all the time I generally go without it. I’m pretty ruthless in uninstalling stuff I’m not using in Chrome and Android. Having said that, I’m not a big fan of having lots of extensions that I only occasionally use. You can use VS Code to write JavaScript, C#, CSS, HTML and a raft of other languages, use its native support for Git and install extensions for AL (obviously), developing Azure Functions, integrating with Azure DevOps, managing Docker, writing Power Shell, adding support for TFVC… Maybe you can teach me something about how you use it – post a comment. This post contains a few of the things (5 to be precise) that I’ve done to make it work better for me. Visual Studio Code has moved quickly from “what’s that? Part of Visual Studio? No? Then why did they call it that?” to become the hub of much of my daily work.
0 kommentar(er)
