Very useful extension that is one of the first extensions I always install after installing VisualStudio. Makes life for many not so common development tasks (e.g. edit project/solution file, ...) so much simpler.
One tip for the developer of this extension (if you don't know already). The extension now has about ~8.5MB in size (The largest I've seen till today, if I remember correctly). If you extract the VSIX and rezip it with for e.g. 7-Zip in Ultra compression mode it will only have ~3.8MB and will still simply work. I know in times where nearly everybody has DSL it doesn't matter that much. But why download 8.5MB when you can achieve the same thing with 3.8MB :-).
Exception Type : Microsoft.Practices.Unity.ResolutionFailedException
Exception Message : Resolution of the dependency failed, type = "SquaredInfinity.Foundation.Configuration.Services.IConfigurationService", name = "(none)".
Exception occurred while: while resolving.
Exception is: InvalidOperationException - The current type, SquaredInfinity.Foundation.Configuration.Services.IConfigurationService, is an interface and cannot be constructed. Are you missing a type mapping?
UPDATE: Putting this back up to a 5. I sent Jarek an email, and he had already (within 10 minutes) updated the extension to address my issue. I can't complain about that kind of turn-around!!!
For reference, 22.214.171.124 fixed the problem found in the issue below. ==========================================================
Exception Type : Microsoft.Practices.Unity.ResolutionFailedException Exception Message : Resolution of the dependency failed, type = "SquaredInfinity.Foundation.Configuration.Services.IConfigurationService", name = "(none)". Exception occurred while: while resolving. Exception is: InvalidOperationException - The current type, SquaredInfinity.Foundation.Configuration.Services.IConfigurationService, is an interface and cannot be constructed. Are you missing a type mapping?
Hi There, Last build didn't play well with DevExpress addin due to compatibility issue. It has been fixed now, so you can either get latest version of VSCommands or latested build of DevExpress addin from http://www.devexpress.com/Support/Center/Issues/ViewIssue.aspx?issueid=B230186
Getting an exception when starting visual studio 2012 premium.
Have to uninstall, it's unusable as it is.
Exception Type : Microsoft.Practices.Unity.ResolutionFailedException
Exception Message : Resolution of the dependency failed, type = "SquaredInfinity.Foundation.Configuration.Services.IConfigurationService
Where can I report this bug?
EDIT: Yeah, it's fixed. I'm yet to explore the goodies and then I'll give my rating =]. Thanks Jarek
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.
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).
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,
Latest release (126.96.36.199) 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
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).
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.
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.
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(188.8.131.52) then add API Controller function will fine.
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,
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.
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!
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.
it apparently still a problem with the compatibility to give Entity Framework Power Tools Beta 3, running VScommands 184.108.40.206 (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?
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.
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.