I see that PowerCommands for Visual Studio 2010 supports visual studio 2012, but it was last updated in Aug 2010. Is there a new "PowerCommands for Visual Studio 2012" or is there a viable replacement?
You don't need a replacement. If you install the Power Commands again, from within VS 2012 (Tools -> Extensions and Updates), it will be applied to VS 2012.
From here:
Just reinstall, even if you already have it for VS2010. The reinstall will then apply it to VS 11
I just did it, and it worked perfectly.
Edit
Productivity Power Tools
Microsoft Visual Studio Team Foundation Server 2012 Update 1 Power Tools
For Visual Studio 2013, it looks like Power Commands is now part of Power Productivity Tools.
I ended up using VSCommands for Visual Studio 2012. This tool provided all I needed from PowerCommands and more.
Most of what was in the Productivity Power Tools are now part of VS 2012. There are a few items missing, afaik, what are you looking for in particular ?
As mentioned on the Productivity Power Tools 2012 page, the Power Commands were added to that addon.
Download the VS2010/2012 version from the VS Gallery.
Unzip the .vsix to a folder (i.e. using the great 7zip), it's just a zip file.
Edit the extension.vsixmanifest file and add this element after the 11.0 one:
<VisualStudio Version="12.0">
<Edition>Pro</Edition>
</VisualStudio>
Repeat for every future version of VS that comes out ;)
Now re-zip the contents (files, not the root folder, so that the extension.vsixmanifest is at the root of the zip file, not within a folder), rename the zip file to .vsix, and double-click to install to all your newly supported editions.
Enjoy!
Related
I have StyleCop installed on my Visual Studio 2015. But, it does not give the option for running StyleCop on one particular file (on right click). StyleCop only runs on build. I am not getting the StyleCop setting option too. I have Visual Studio 2015 professional edition and I have install StyleCop from Codeplex. I have installed it using Nuget Package Manager.
You can try Visual StyleCop, which is an extension to Visual Studio. This preports to give the right click functionality into Visual Studio 2015
StyleCop.Analyzers gives you something close to the old right click functionality, but at a project level, not a file one. Let me know if you want more info on it.
Update 11 Feb 2016 There is an alpha release of StyleCop (4.
7.50) with Visual Studio 2015 support (but not C# 6).
Update 16 Oct 2018 StyleCop is mainstream available up to VS2017. Options in VS itself are provided by the extension, not the nuget package.
I have a project written in PowerShell and I want to create an interface for it using Visual Studio 2012. How can I load the .ps1 file in Solution Explorer? I have already run through these steps:
http://nickmeldrum.com/blog/how-to-run-powershell-scripts-from-solution-explorer-in-visual-studio-2010
(the steps are for Visual Studio 2010 but I thought the settings shouldn't differ too much) but now I don't know what to do...I have to install some tools or something?Thank you!
You haven't specified what's the issue here. Steps from the linked article should work with Visual Studio 2012 without any adjustments as far as I see. Make sure that you followed those steps correctly.
BTW, you may want to install "PowerShell Tools for Visual Studio 2012" extension.
I installed the free version of ApexSQL which is awesome in SSMS, but I really don't want all those menus in Visual Studio. I went to add-in manager and unchecked them, but the Startup column is checked and disabled so every time I restart Visual Studio they come back.
Is it possible to permanently remove the ApexSQL menus from Visual Studio?
If you have ApexSql installed and you don't want those pesky menus in Visual Studio do 2 things.
In Visual Studio, go to Tools > Add-in Manager and uncheck the ApexSql addins. Close Visual Studio.
In Windows 7, there's a hidden folder C:\ProgramData. In Windows Explorer go to C:\ProgramData\Microsoft\MSEnvShared\AddIns folder. Edit each of the *.MsvsLoader.Addin files and set <LoadBehavior> to 0. If you can't save the files directly, you'll have to save the files to a different location (desktop maybe) and then copy them back into C:\ProgramData\Microsoft\MSEnvShared\AddIns because there's some Admin privilege required.
Now when you restart VS those ApexSQL menus should be gone
The issue of crowding menus is resolved in latest releases, now all ApexSQL add-ins are under the main ApexSQL menu as sub-menus. They look like this now:
If you don't need ApexSQL add-ins in VS or SSMS you can simply choose not to integrate them with VS or SSMS during the installation, just check out SSMS ot VS version in which you want the add-ins integrated
Note: To get this dialog in which you can check the wanted integration you need to use individual installers not the main one. You can find all individual installers on this link
Disclaimer: I work for ApexSQL as a Support Engineer
For Visual Studio 2010 on Windows 7, I attempted #Chris Bayles suggestion and do not see ApexSql addins under Tools->Add-in Manager.
I followed #Jerome2606's pointer to https://knowledgebase.apexsql.com/remove-add-ins-just-visual-studio-retaining-sql-server-management-studio/ and it worked for me, but only when I removed the parent ApexSQL folder as well.
Summary of what is required to do:
Remove folder
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\ApexSQL
Depending on the version of Visual Studio, the version number in the default installation location will be different:
Product name Version number
Visual Studio 2010 Microsoft Visual Studio 10.0
Visual Studio 2012 Microsoft Visual Studio 11.0
Visual Studio 2013 Microsoft Visual Studio 12.0
Visual Studio 2015 Microsoft Visual Studio 14.0
Select and delete the ApexSQL folder and its contents.
Open Command Prompt as an administrator, then run
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" /setup
Please note the command is different for Visual Studio 2012, 2013, and 2015.
If you are using SSMS v18.0 then you can disable the apex features in following way.
You can find the ApexSQL.Complete.Addin.SSMS18.pkgdef file from following path.
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Extensions\ApexSQL Complete
Then open this file in Notepad++ Administrator mode and comment the content.
If you need further reading follow this link.
https://knowledgebase.apexsql.com/remove-apexsql-tools-sql-server-management-studio/
I have a newly built Windows 8 VM with VS 2012 Premium running on it, when I try open any sln file I get the following modal pop up error
Visual Studio 2010 Shell
Invalid license data. Reinstall is required.
I can open the sln's if I open up VS and then do project open, this is really annoying, any ideas how I fix it?
*Note I have done a VS repair and it didn't solve it...and I never had any VS RC release on the machine, all new build with s/w downloaded from the MSDN
Cheers
I encountered the same exact error when I created a solution with a full version of Visual Studio 2012 Professional on one machine and then tried to open the solution file with a copy of Visual Studio 2012 Express on a different machine. I got the error when double-clicking the solution file, but not when loading the solution into an already opened instance.
I fixed the error by opening the solution file (.sln) with notepad and changing the line that says Visual Studio 2012 to say Visual Studio Express 2012 for Windows Desktop.
After that, I was able to double-click to open the solution file on the machine that has Express installed.
I'm using VS 2013. I fixed this by right clicking the .sln and setting the Open With parameter to visual studio 2013 and not VS version selector or VS 2010.
I have faced the same problem. When I set the system Date and Time to the current Date and Time, The Problem solved by itself.
It looks like the .sln extension is owned by "Visual Studio 2010 Shell" a minimal version of Visual Studio that ships with products like SQL Server and Office to provide support for add-in development without any other features. Since this is a minimal version, it's unable to load any project type that ships with Visual Studio Express, Professional or above.
The same may happen when you have Visual Studio Express installed next to a full version of Visual Studio.
This may happen when you install an older version of Office or SQL Server after having installed Visual Studio. The old installer will hijack the extension.
To repair this problem:
use the "Open With" option of Windows and select the "Visual Studio Version Selector" as your default action.
Or open the "Default Programs" option in Windows, look up the .sln extension and make sure it uses the "Visual Studio Version Selector" as default:
Or locate Visual Studio 2012 in the Programs and Features window of Windows and chose "Change", the Visual Studio installer will pop up, chose "Repair" to have it repair the file associations and any other problems that may arise by installing Visual Studio versions in reverse order (it may for example mess up the MsBuild directory as well).
Remember that when Visual Studio 2010 was released, it could not yet know what Visual Studio 2012 would change, as such, it's best to install versions of Visual Studio in the order they were released. This may sometimes prove difficult, as other products may install Visual Studio versions without you knowing.
can i install and use, visual studio 2008 and visual studio 2010 on the same windows xp/vista
have visual studio 2008 installed and working
wnat to install visual studio 2010 and use with 2008,
some solutions on 08 and some on 10..
any problems possible?
Yes, you can!
Can't add anything else, honestly! :)
Well, I personally have 2005, 2008 and 2010 installed on the same workstation, for various needs and projects. Works without any problem!
No problems at all running both Visual Studio 2008 and 2010 side-by-side. My development box is currently set up this way.
Solutions will automatically open in the version of Visual Studio that they were created in. You can manually choose to open them in a newer version, but you will need to update them. A wizard will automatically appear that guides you through the process.
Opening a solution saved with a newer version of VS in an older version is not a supported scenario.
But there is a workaround: simply open the *.sln file in a text editor (like Notepad) and decrement the version number by 1. You'll have to do the same thing for each of the project files.
I had the same problem with converting a Visual Studio 2008 project to 2010, which made the program could not compile at all with every measure i took.. then I installed Visual Studio 2008 again and it turns out they can be installed in the same computer and work, but you need to open visual basic 2008 manually if you want to develop a project there..
You shouldn't have any problems unless you try to develop for Windows Phone 7, which you can't currently, and may never be able to, do in Windows XP.