VSCommands for Visual Studio 2012

I find Directory Explorer very useful to drag-drop files into projects (elevated). When you first start Directory Explorer it shows the Desktop folder. 
When you navigate to a different folder this is remembered throughout the VS session. The Desktop contains the "Control Panel" item. If you navigate to Control Panel, there is no way you can go back to normal folders, since the tree is not displayed, keyboard shortcuts don't work and there is no address bar or buttons to go back, up or whatever. You will have to restart VS. 
Also, it would be useful if multiple instances were allowed, each with independent navigation.

Thank you for great feedback!
I just tried it and you're right, there seems to be no way to go back from control panel. I will try to fix it shortly and also add support for multiple instances.

IMHO, an address bar and a home/back/forward/up set of buttons would be fine to start with (global "home" for now). If you plan to add multiple instances, then I'd suggest to consider the possibility of defining a "home" directory at the project level (i.e. each project has its own associated home directory).

Hi,

we're trying to change the color of error texts in the output windows. Unfortunately there is no VSCommands group in the Fonts and Colors settings (checked on several clients). We've tried to reinstall the extension, to reset all settings, to start with Administrator privileges, but the VSCommands group is still missing. Other functionality of the extension works like expected.

We use VS 11 Premium Update 1.

Thanks in advance,
Sebastian.

Hi Sebastian,
Latest release (1.2.6.0) has option to recreate VSCommands group (Tools | VSCommands | Options | IDE Enhancements | Output Windows). You can read more here: http://vscommands.squaredinfinity.com/release-notes/2.6.0

Hi Jarek,

unfortunately the new option didn't solved the issue. When clicking the button an error message occurs. I've started the VS with /Log and will send you the log files by e-mail. The VSCommandsLog.txt will contain a trace of the exception (System.Security.Principal.IdentityNotMappedException).

Thanks,
Sebastian.

Out of curiosity I ticked the checkbox in the Attach To IIS window and now cannot reset that value. I've gone through the various setting windows but can't see anything. Is there a way to reset this?

Yes, the dialog will show again if there's no solution open of if solution has no web projects in it.

You can also bring it back at any time by holding Ctrl when clicking Attach to IIS.

I'll update the tooltip on this button to make it more discoverable.

Cheers,
Jarek

Super thanks Jarek. Keep up the great work.

I'm noticing some weird behaviour with the "Change Window Title".

First, there are two "Change Window Title" menu items when I right-click on the VS2012 title bar.

Second, the two options don't seem to be in-sync. For instance, I click on the first one and change the title.  When I click on the second one, it doesn't show the new value.

Also, if I change the title, the solution badge shown when I "Alt-Tab" in Windows 7 seems to be switching back and forth (very quickly) between the default title and my custom title.

I tried uninstalling and reinstalling VSCommands, but it didn't make any difference.

Hi!
Thank you for reporting this problem.
I managed to reproduce it locally and fix should be ready for release this weekend.

Cheers,
Jarek

Hi,

Latest release should fix this.

Cheers,
Jarek

Windows 8 + Visual Studio 2012 Update 1 + Web Tools 2012.2.
I found a problem setup Web Tools 2012.2 after. 
In ASP.NET Web API project (C# / VB.NET Same), use Database first(Create new SqlLocalDB) + Entity Framework(add to Models), Then I want add new API Controller with EF (CURD Action), will show error message.

'ProjectName.ClassName' is not part of the specified 'ProjectName.???Entities' class, and the 'ProjectName.???Entities' class could not be modifed to add a 'DbSet<ProjectName.ClassName>' property to it.（For example, the 'ProjectName.???Entities' class might be in a compiled assembly.）

I disable VsCommand(11.2.5.1) then add API Controller function will fine.

Hi, 
Thank you for letting me know about this issue.
I will try to reproduce it locally later today.

Could you please try to run Visual Studio in diagnostic mode (i.e. "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe" /Log), try to repeat the steps and email log files to Jarek@squaredinfinity.com ?
The log files are located in C:\Users\<username>\AppData\Roaming\Microsoft\VisualStudio\11.0
(ActivityLog.xml and VSCommandsLog.txt)

Thank you in advance,
Jarek

ASP.NET MVC 4 with .NET 4.5 has the same issue.  Hope this can be fixed soon.  Thanks!

Hi Squared Infinity [Jarek Kardas],

Here is the way to reproduce this problem. Hope that helps!

1. Create a project
2. Select .NET Framework 4.5 Target
3. Select ASP.NET MVC 4 Web Application
4. Choose Internet Application
5. Create a Model using Entity Framework (Database First)
6. Build Project
7. Add Controller
8. Enter Controller Name & Choose a Scaffold Template & Choose existing Entity Class & Data context class
9. Press "Add" button, then error occurred.

If you disable VSCommands for Visual Studio 2012 extension, then there is no error occurred when adding controller with scaffold template into ASP.NET MVC 4 with .NET 4.5 project.

Hi!

Thank you for update on this issue.
I believe that this is caused by VSCommands using Enity Framework and Code First internally, which doesn't seem to go well with other extensions that do similar thing. I managed to remove dependency on EF and CF but will need another day or two to complete testing. The fix will be available shortly!

This should be fixed in latest release.

Thanks,
Jarek

Is it possible to add menu item that create a copy from linked item.
It will then copy linked file into appropriate directory and change link into item addition

Hi, 

Could you provide bit more information about your usage scenario?

It is now possible to copy linked files between projects (using ctr+c/ctr+v in Solution Explorer).

So, real scenario:
I have WP8 project as main and also link files from that project to WP7 project using ProjctLinker 2012. Hence when I add file to WP8 project it is automatically linked to WP7 project.
So I've been writing code in WP8 project and used some features not supported in WP7. In this case I want to copy whole file from WP8 project and replace its link in WP7 project with a copy of this file.
To perform this now I need to delete link, and copy-paste file from WP8 project to WP7. I ask if it is possible to automate this actions in the way that I click on linked file, choose "Copy source and replace link" and VSCommands perform described actions.

I see what you mean now.
Will have a look and see what can be done.

Thanks,
Jarek

Hi,

it apparently still a problem with the compatibility to give Entity Framework  Power Tools Beta 3, running VScommands 11.2.5.1 (Visual Studio 2012, W8x64)

A constructible type deriving from DbContext could not be found in the selected file.

When i deinstall VSCommands, EFPowerTools Beta 3 still works.

Is there something that can fix this issue?

Best regards
Alexander

Hi Alexander,

While this compatibility issue seemed to have been fixed for EF Power Tools Beta 2, it appears that some changes introduced in Beta 3 made the problem come back.

I am working on a long term fix right now.
Starting with next release VSCommands will no longer depend on Entity Framework or Code First which should prevent this issue from happening in the future.

The fix will be ready by the end of this week.

Thanks,
Jarek

Okay that's good news!

Zip Solution does not exclude vssver2.scc files in third-level subfolders:
root/dir1/dir2/dir3/vssver2.scc

Good spot, I'll try to fit the fix in the next release (later this week).

Could you include a configuration setting to disable the Unhandled Exceptions Monitoring, or atleast one to disable the 'toast' pop-up.

Sure, will add in next release!

Why have you decided not to integrate with native Visual Studio settings window?

Good question. Main factor was usability. Visual Studio settings window is quite small and cannot be resized. It is also a modal dialog window, so to see results of setting changes you have to close it and, if you need to tweak configuration bit more, open it again.