Alt Dot Net Usergroup: Does the world end if you stop using Visual Studio?
Download as PPTX, PDF0 likes622 views
This document provides an introduction to using Vim as an alternative to Visual Studio for C# development. It discusses Vim's modes, basic editing commands, buffers, syntax highlighting, creating macros and functions, refactoring, spell checking, scriptability, navigating and interacting with code, building projects, source control integration, bookmarks, code completion, extensions, folding code, debugging, and next steps for enhancing it as an IDE for C#.
![QuickFix Example: Find In Files:vimgrep (or :grep if you have the actual program)Fills the QuickFix list:vimgrep /[pattern]/[g][j] {file}E.g. :vimgrep /public/j ./**/*.cs[g] == Include ALL results as separate lines[j] == Don’t jump to first resultCan also use :lvimgrep (or :lgrepif you have the actual program)Fills “location list” which is local to current windowUse :lw or :lopen to see this:lolder and :lnewer to navigate search result history](https://image.slidesharecdn.com/20100716altdotnetusergroup-doestheworldendifyoustopusingvisualstudio-110416102455-phpapp02/85/Alt-Dot-Net-Usergroup-Does-the-world-end-if-you-stop-using-Visual-Studio-16-320.jpg)
![TagsBuild them using Exuberant Tags (ctags.exe):tag <tagName>Jumps to a tag:tagsGives a list of all tagsCTRL-g == navigateg] == listSets a mark upon navigationAllows you to return to the same spot](https://image.slidesharecdn.com/20100716altdotnetusergroup-doestheworldendifyoustopusingvisualstudio-110416102455-phpapp02/85/Alt-Dot-Net-Usergroup-Does-the-world-end-if-you-stop-using-Visual-Studio-20-320.jpg)
Alt Dot Net Usergroup: Does the world end if you stop using Visual Studio?
- 1. Does the world end if you stop using Visual Studio?Hint: No.
- 2. Who Am I?Garry StewartI do tehsoftwarezContact me garry.stewart@gmail.com@garry_stewarthttp://www.garry-stewart.com/
- 3. IDE AddicitionGeneral text editingSyntax highlightingIntellisenseWYSIWYG EditorsVisualisation toolsCode generationBuild management & compilationCode navigationFile managementSource controlIntegrated debuggingEtc…
- 4. This used to be Less Complicated, Right?
- 5. So let’s All Develop In Notepad!
- 7. Before We Start..Current directory is king%PATH% mattersCommand line tools are your friend
- 8. There are these things called modes…Lots of different modesInsertVisualNormalAnd More!You will spend most of your time in Normal mode.You cannot enter text in this mode
- 10. Basic Editing:help operator:help scrollingEverything has a count5dw == delete the next 5 wordsRinse and repeat. Repeats the last command
- 11. Stuff to Get Into if We Have Time:help buffersSyntax highlightingCreating functions and macrosRefactoringSpell checking
- 12. Ultimate PowerFully scriptableOn the fly via commandsPlugin architectureBuilt in Regex engineReassign key commandsInteract with the command lineMacrosNo COM required to create extensions!
- 13. Navigating Code:help various-motionsCurrently “broken” for C# if you have a namespaceIt’s all just regex, so we can extend this to work with
- 14. Interacting With The Command Line:! <command> == execute a command (opens a new window):r ! <command> == read the output of the console operation into the current bufferHave a custom function in my _vimrc to print output in a new window
- 15. QuickFixQuickFix == list of search results with file navigation:copen or :cw " Open the quickfix window:ccl " Close it:cn " Go to the next error in the window:cnf " Go to the first error in the next file:colder " Look at older results:cnewer" Look at newer resultsGlobal to all windows
- 16. QuickFix Example: Find In Files:vimgrep (or :grep if you have the actual program)Fills the QuickFix list:vimgrep /[pattern]/[g][j] {file}E.g. :vimgrep /public/j ./**/*.cs[g] == Include ALL results as separate lines[j] == Don’t jump to first resultCan also use :lvimgrep (or :lgrepif you have the actual program)Fills “location list” which is local to current windowUse :lw or :lopen to see this:lolder and :lnewer to navigate search result history
- 17. Building a Project:makeUses makeprg to tell what to executeMSBuild in my caseUses errorformat to parse build output for errorsRedirects errors to QuickFix windowEquivalent of Visual Studio’s build error list
- 18. Source Control IntegrationDidn’t we already cover this with command line integration????I’m using gitRunShellCommand to the rescue again!
- 19. MarkersBasically bookmarksSome set by Vim functionsCan be set by you:help mark-motions
- 20. TagsBuild them using Exuberant Tags (ctags.exe):tag <tagName>Jumps to a tag:tagsGives a list of all tagsCTRL-g == navigateg] == listSets a mark upon navigationAllows you to return to the same spot
- 21. Code CompletionSort of worksCan’t get it working like Intellisense with C#Works fine in C/C++/Java/Pretty much anything elseSeveral types of completionOmni CompletionIn File completionMany more..
- 22. ExtensionsHuge plugin communitySome samples:NERDTreeBasically Solution Explorer:TlistToggleClass view using Tags
- 23. Folding CodeYes, you can do itNo, I haven’t looked at itThink of this as an equivalent to #regionRegions are evilUseful when building pluginsNERDTree and TagList both use it
- 24. Next StepsGet “intellisense” working properlyOr just learn the BCL…Generate tags from BCL source codeTry to get command line debugging working via Shell calls and the Quickfix listStart creating refactoring and code generation functionsE.g. extract method, create controllerTake a look at http://vim.wikia.com/wiki/Vim_as_a_refactoring_tool_and_some_examples_in_C_sharp
- 25. Closing Thoughts