VS does not allow me to copy a file from solution explorer and paste into a Windows folder. Let's leave aside how asinine that is for starters, and install a solution.
Well, none of my projects load after installing the extension: error dialog after error dialog. Does anybody ever ponder just how sloppy the design/implementation of this extension or the extension system has to be to allow it to render all of your projects useless? Any consideration of the cost to end users of a system this brittle? Thankfully the UNINSTALL worked.
Very handy, but same comment as iters, very annoying pop-ups saying that the version expires in xx days, each time one opens VS.
Despite what was replied to him, this is still there. I don't believe in a system for which every plugin regularly requires attention and block the opening with a pop-up. I believe there is an update functionality in VS, it should be used instead.
Can VsCommands show the full solution path?
Maybe in the title bar?
And how about the full path to files too?
This post on StackOverflow seems to suggest that VsCommands can do it...
...but I cannot find the option in the VsCommands version for VisualStudio 2013.
Can it be done? If yes, then exactly how?
-- Mark Kamoski
I want to add to the critical mass of requests for VSCommands for VS 2015. I have my team using it and it's such a life-saver for me personally, especially the functionality that puts the branch / tfs path names in the title bars and task switcher. What's the holdup? Is there anything the community can do to help get it working/released for vs 2015? Do you need beta testers? Do you need help solving bugs? Do you need funding? I'm sure there's folks here that are willing to help with all these things.
Any update would be appreciated. Thanks!!!
It'd be sad for a great tool like this one to go down the drain, not for lack of beta testers nor funding, but from lack of clarity\openness from its authors... Please let the community know how it can help. Thanks again for the great work thus far.
As much as I liked this extension (enough to pay for it), I believe it is safe to assume the author has let it die. Supposedly it went open source but the repo on GitHub shows only the vsix and not the code - and that was updated 7 months ago.
Time to find other solutions.
1. Branch name etc in title bar - look for "Rename Visual Studio Window Title" extension.
Please reply with other replacement extensions.
Hi, sorry for a delay, early version of 2015 is available here: https://visualstudiogallery.msdn.microsoft.com/c84be782-b1f1-4f6b-85bb-945ebc852aa1 (though it's getting unpublished by administrator for some reason)
It's a complete rewrite but also open source (on github).
So far Solution Badges has been migrated, I'm going to add more features soon.
The extension is really great, I have used it for years. Thanks for your great work!
However I find two very useful command are missing for some kinds of editor context menu, such as cshtml and css types. Can you think of that? Thanks again.
Since my update to v18.104.22.168, the build output window coloring doesn't seem to work any more.
The build summary appears as configured, but the coloring isn't there.
I tried the button "Recreate Fonts and Colors category" in Options, but unfortunately it doesn't help.