I like the *idea* of what you've done here. And I'm currently using it in lieu of the Snippet Designer extension I was previously using.
However I find the "click on an empty line, right-click, select 'Edit Snippet", then finding the file to edit" method of editing a snippet a bit unintuitive & clumsy. You have to actually have known about the blog post & read it to even know this method of editing exists. Hence the comments about "editing doesn't work".
Secondly, it would be much better if on opening a .snippet file, that this editing process was opened for you. As it is now, if I open a .snippet file I get the very XML view of it that you're trying to avoid with the extension.
Oh, one more thing. In the "Snippet Preview", there's no visual indication of where the "fields" are. You have to know where to click in the code in order to be able to set/change any of the field properties.
Are you going to open source the extension? I'm sure a lot of people would like to contribute via pull requests to improve the experience.
Looks great but can't use it "The extension requires a version of the .net framework that is not installed" Come'on! Do you need 2.0 or something? How about telling me? This is a dev machine with every permutation of the .net stack since 2013 installed on it.
I used the Snippetizer to make a snippet with ease. But then it killed my Peek functionality in VS2013. It prevented me from dismissing the Peek window by pressing Esc. So, I removed it. Sorry Snippetizer.
Nearly perfect! Editing a Snippet in raw XML is a torture. This Extension makes it easy to create custom snippets and edit existing ones with all needed properties. The only weird thing is, that the commands in the Edit menu are not disabled if they unavailable.
I've made snippets in the past, but hand making the xml and remembering the tags/structure has always been friction. I just easily made two new ones. I feel a new library of custom snippets coming on! Sweet!
Include in the next update of VS, please!!! :) Very useful!! I´m a Technical Educator for Windows Internals and C++ (always using VC++), and I have to create groups of blocks of code to my samples and this kind of tool helps a lot.
Roger Villela Technical Educator for Windows Internals and C++.
It seems interesting with basic features and the way you edit is really nice, however the Snippet Designer seems to work better for me. I got invalid snippet file when I tried to edit an existing snippet. I had to reedit it in Snippet Designer to get it back working.
I think with a little more work it could be a good alternative.
Microsoft asks us so much for the feedback ("Let us know what you think! We're constantly going through questions and reviews here on the gallery, so please - do let us know what you think!), but then nobody from the team wants to answer the questions posted here. Why bother to write reviews then?
When I'm thinking about "upgrading"(?) to newer version of Visual Studio, I'm always afraid that:
- my favorite extensions will no longer work
- my favorite features will be removed (see e. g. macros)
- projects that I created will no longer work
- a few simple to fix but annoying bugs will not be fixed (e. g. "What happens when you for instance are trying to update two tables that are related at the same time ? Well, you get an SqlException (...)" - this bug at dates back at least to VS2005 and is still present in at least in VS2010)
- new bugs (or similar) will be added (e. g. "I've just found out that in Visual Studio 2015 they decided to add some additional c# triggers for auto-formatting but not give us an option to turn it off. From what I have seen, in certain circumstances colon and open curly brace now causes an autoformat.")
- a few simple but useful features that I wait for years will not be added
- but a lot of useless stuff will be added, so IDE will work much slower (but this should go without saying)
So yes, I think that "upgrading" to the newest version of Visual Studio is worth the time (and money)...
P. S. For 2015 there is a free extension "Snippet Designer":
but it doesn't support IntelliSense and is slightly buggy. For editing existing snippets "SnippetEditor" works better for me (but Snippet Designer is better for creating them).
As for closing "peek definition", try Shift+Esc like with tool windows (just my idea, I use VS 2010, so no peek definition here in a strict sense, just "Code Definition Window" which is a tool window).
First off, GREAT JOB!!! This is exactly what I needed.
I am having some issues on vs2013 premium using C++ projects. Are there any know bugs around this? It is crashing my IDE when i press, Save. Are there any logs that i can review or collect?
ActivityLog.xml from VS returns the following when i add to the Snippet Definition. Followed after that i press, Save and that's when VS crashes.
<source>Editor or Editor Extension</source>
<description>System.NullReferenceException: Object reference not set to an instance of an object.
at Company.Snippetizer.VariableManipulationHandler.OnSelectionChanged(Object sender, EventArgs e)
at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.RaiseEvent(Object sender, EventHandler eventHandlers)</description>
I can get the snippets to save okay, but once I edit one and save it, I can no longer EDIT that file because it has changed the language element from "BASIC" to "VB", which causes an error on loading for EDIT. I can still INSERT the snippet though.