munyabe / caseconverter Goto Github PK

Just installed in VS2015 Community Ed. & restarted on a Win 10 64bit machine that also has VS 2013 Community Ed. and VS Code. While cursor is on a word (word not selected), as soon as key binding is pressed (CTRL+SHIFT+K, CTRL+SHIFT+C), following error dialog shows and nothin happens to underlying text:

Are we doing anything wrong? Thank you

A few useful additions I think!

@BrainCrumbz wrote on #2 :

It could be a nice-to-have feature if extension could detect the word underneath cursor, when nothing is selected. Basically the same happening as when you press F2 to perform rename refactoring. Just our 2 cents. Thank you!

The keys not working with Visual Studio 2017
Ctrl + Shift + K, Ctrl + Shift + C
Maybe you need to let users to set the keys.

It would be nice if I could select multiple string values (Using VS2017's new multi-cursor functionality) and convert them.

When the extension is installed from Visual Studio Glery, it doesn't work when invoked.
A message box with error message is displayed. It points to the exception log.

This is a entry from Visual Studio Exception Log:

VovaP wrote on Visual Studio Gallery.

There are some problem with HTML. I receive the error message until trying to uncomment . (https://www.dropbox.com/s/flq2zo23snzqkbb/snap01.PNG?dl=0)
In the same time the Visual Studio command "uncomment" works properly.

It would be super helpful to have a second menu option to convert case in the opposite of the order set in options. So if the order was such that invoking the standard command would convert an identifier in camelCase to PascalCase, then invoking the alternate command on an identifier in PascalCase would convert it to camelCase in 1 step instead of having to loop around.
It could be bound to Ctrl+Shift+K, Ctrl+Shift+U for symmetry with the comment commands by default.

Figure 1. The Convert Case command shows up on the Edit, Advanced menu even though no text-based file is currently open and available in the editor.

Issue Summary

The Convert Case command is displayed and not greyed out when there is currently no file open in the Visual Studio editor, even though this should not be the case.

Expected Behavior

When the extension is installed, and there is currently no active text-based document open, the command either should not be visible and/or it should be greyed out.

Steps to Reproduce

1. Install the extension.
2. Launch Visual Studio.
3. Open a Solution if you wish, but make sure there are no document tabs showing, or that there are no text-based or source files currently open in the Editor (i.e., those sorts of files to which this command might apply)..
4. Click the Edit menu, and then point to Advanced.
5. The Convert Case command is shown and selectable.

All the casing options available in Microsoft Word are great examples of casing options that are useful for text editing in general, not just for variable names. These would be very helpful additions.