I'm trying to add a new C/C++ file item in Visual Studio 2013. However, when I clicked "add new item", there's absolutely nothing under "installed". I'm looking for Visual C++ > C++ under installed.. What could be wrong?
Is there anything I should be installing?
Under "Online", I only see templates>visual c#.
Thanks for any help, Google is returning nothing for this.
This is a bug in the Visual Studio Express for Windows Desktop installation. They forgot to change a registry key to reflect the different directory structure for the express installation compared to the full software.
It is listed in the Workarounds tab and pasted here for reference (originally from Microsoft Connect, which was retired). Works like a charm.
...update TemplatesDir location in registry. The key to update is given below.
[HKEY_CURRENT_USER\Software\Microsoft\WDExpress\12.0_Config\Projects{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC943}\AddItemTemplates\TemplateDirs{F1C25864-3097-11D2-A5C5-00C04F7968B4}/1]
"TemplatesDir"="C:\Program Files (x86)\Microsoft Visual Studio 12.0\\VC\VCProjectItems_WDExpress"
Related
This has been the case unfortunatly for the past couple of months. I can't install new or update packages from Tools ==> Extensions and Updates I tried everything, yet I am unable to find the reason.
I've tried :
Access NuGet and download packages from "Package Manager Console" Install-Package = SUCCESS
Access repositories using Web browsers, Visual studion internal browser = SUCCESS
Same window in Visual Studio 2010 = SUCCESS
Visual Studio 2012 - Doesn't work
Visual Studio 2010 - Works!
As it turns out for some reason -possibly due to an RC-, My registry settings were pointing to a different url that was getting redirected.
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config\ExtensionManager\Repositories
AND I changed
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config\ExtensionManager\Repositories{0f45e408-7995-4375-9485-86b8db553dc9}(Default)
to
http://visualstudiogallery.msdn.microsoft.com/Services/v2011/Extension.svc
instead of
http://go.microsoft.com/fwlink/?LinkID=251029
I changed
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config\ExtensionManager\Repositories{aeb9cb40-d8e6-4615-b52c-27e307f8506c}(Default)
to
http://code.msdn.microsoft.com/Services/v2011/sample.svc
instead of
http://go.microsoft.com/fwlink/?LinkID=251031
Remove the local cache of extensions and download them all again.
The easiest thing to do is to rename
%LocalAppData%\Microsoft\VisualStudio\Visual Studio version\Extensions\
to
%LocalAppData%\Microsoft\VisualStudio\Visual Studio version\Extensions.old\
and run visual studio, it will update recreate the folder.
WeSam Abdallah's hint worked perfectly for me! Just try to open the link provided in HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0_Config\ExtensionManager\Repositories{0f45e408-7995-4375-9485-86b8db553dc9}(Default) in your browser and see what it is changed to automatically. For Visual Studio 2013 I had to change the URL from https://go.microsoft.com/fwlink/?LinkID=309922 to https://visualstudiogallery.msdn.microsoft.com/services/dev12/extension.svc
This answer is an update for Visual Studio 2015.
I tried the registry hack as well as renaming the Extensions folder, and neither solution worked.
However, in my case, the issue seems to have been because I'm behind a proxy at work. This worked for me:
https://stackoverflow.com/a/32650801/2452084
I have visual studio express 2012
and it was working fine earlier I had run my solution once. But now when I do it, there appears a dialog box with the message!
the Microsoft.VisualStudio.Web.PasteJson.JsonPackage, Microsoft.VisualStudio.Web.PasteJson package did not load correctly.
the problem may have been caused by a configuration changhe or by installation of another extension. You can get more information by exmamining the file
C:\Users\AppData\Roaming\Microsoft\VWDExpress\11.0\Log.xml
continue to show this error message?
How do I get rid of this error?
I started to see this on the fresh windows & VS 2013 Ultimate with Update 2 installation.
To resolve the problem, close all Visual Studio instances head over to
C:\Users\<your users name>\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache
and delete all the files in the folder.
It worked fine for me. Thanks to this article.
Not relevant to VS 2012 express, but I experienced this problem with VS 2013 Premium. I had recently added the productivity power tools extension. To get back up and running, I loaded Visual Studio in safe mode:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE>devenv /safemode
And un-installed the productivity tools. The errors went away.
You need to clear the ComponentModelCache folder or rename it. For Visual Studio 2013, it’s located in the %LOCALAPPDATA%\Microsoft\VisualStudio\12.0 folder.
Refrence:
http://www.rajapet.com/2014/02/when-the-editorpackage-does-not-load-correctly.html
I had Visual Studio 2013 Professional and I got the same error. I couldn't remove it until I repaired VS installation. It took a while but now it works fine.
I had this problem as I had an older version of VS2012 Express (release on Web Platform installer dated 15/08/2012).
Try installing 'Visual Studio 2012 Express for Web (Latest)' with release date 22/10/2012 from the Microsoft Web Platform Installer.
That is all I did and I no longer get those messages.
I asked this question about VS2010, because the location changed from where it was in VS2008, and I couldn't find it.
Now they've done it AGAIN!!!
So where is it now?
Why have they done this again? Apparently just to keep us on our toes. Remember that it was under a folder in Microsoft Visual Studio 10.0 called VSTSDB? Well, that folder still exists in VS2012, but it is now vestigial. You have to look in another place. In fact it seems to have been migrated back to where it was in an earlier version of Visual Studio. Look here:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\Microsoft\SQLDB\Extensions\SqlServer\Items
Talk about a convoluted path.
I'm trying to move a solution I have over to Visual Studio 2012 and one of the project types is .vdproj.
According to this link this project type is not supported in Visual Studio 2012:
MSDN says they recommend that you use InstallShield Limited Edition for Visual Studio.
The problem is, when I open up my solution in VS2012 and try to add a new "Enable InstallShield Limited Edition" project to my solution, I get an error message saying:
Creating project 'test'...project creation failed.
Why might I not be able to add a project of this type to my solution?
If I make a new empty solution I can't make an InstallShield project it in either.
I'm going to try to download InstallShield limited edition and see if it does anything.
I tried out that InstallShield download, and it added two extra project types, but I'm unable to create either of them. I'm able to add normal website projects to my solutions just fine, but not deployment projects.
The installer was named the same, but this one prompted me to re-start. After re-starting I was able to add an InstallShield project, but it gets created in its own solution. So, it looks like now I have to figure out how to use it, and I'll be good to go.
It's looking like the limited edition doesn't have support to install Windows services.
This will probably be long and boring because there's lots of steps, but I'd like to write up how to move from a Windows service installer .vdproj to the new InstallShield LE that's available in Visual Studio 2012.
Step 1: Create a merge module (.msm)
Follow the steps of this guide.
Notes:
You will need to install WiX 3.6 and isWiX
The latest release of IsWiX doesn't enable the Tools menu item in Visual Studio 2012. Edit the file: C:\ProgramData\Microsoft\MSEnvShared\AddIns\IsWiXAddin.Addin (XML) and clone the HostApplication element and update 10.0 to 11.0.
In step #8 of the guide, it references a code tab. This has been moved to the XML Editor item in the bottom of the left menu
I left the MergeRedirectFolder empty for my installation
Here is my isWix files view:
After you're done with the guide you should have an empty .wxs file that looks something like this:
Using the Component XML element pulled from here you should end up with a .wxs file that looks like this:
Hit build and you should now have a .msm file.
Step 2: Adding merge module to InstallShield
Go though the wizard to setup the basic install information like company and version information.
Find the redistributables view in ISLE. Right click the list and select browse for module. After your module is found and added, right click the modules and select properties. Set the destination folder drop down to INSTALLDIR. I had to set mine to the lowest level folder I created for my install path, so you might have to experiment a bit.
Build Project, and test on virtual machine
Redistributables Screen
If you're getting errors about the path being too long you might need to change the release location to something close to the root.
Here's a list of all the build errors for reference.
Now you should be able to run your installer and have it install/start a Windows service. A lot more work than .MSI files, we got it to generate in Visual Studio 2010, but overall it was not too bad.
While there is no easy or truly supported solution for Visual Studio 2012, Visual Studio 2013 users can get an extension from Microsoft in the Visual Studio Gallery.
I found this post which says you must download InstallShield first. It's a very confusing way to work. I suggest to vote up the post on the connect site and give them comments letting know how poor that is. They could at least give a more descriptive error http://connect.microsoft.com/VisualStudio/feedback/details/732196/project-creation-failed-for-installshield-limited-edition#tabs
I opened my vs2010 solution with vs2012 but it didn't make any conversion as from 2008 to 2010 was happening. So my solution still remains the same as 10 label on it. when I make a new solution of course it has 11 label on it. I haven't got any problem running like that but I am curious. Is there any difference? if yes, how to convert into vs2012 solution?
I managed to 'convert' the solution file to change the line containing '# Visual Studio 2010' to '# Visual Studio 2012' in the .SLN file.
Manual editing of the solution file is not necessary, or recommended. Simply open the VS2010 solution in VS2012, left-click the solution (at the very top of the Solution Explorer), then use File | Save As to overwrite the original file. This will effectively convert the VS2010 solution file to a VS2012 solution file.
There are some exceptions, but mostly you'll be able to open the same project and solution files files in both VS2012 and VS2010 SP1.
VS2012 may convert projects when you first open them, but the changes are (except noted in the document linked) backward compatible with VS2010 (ie using conditionals where needed to only apply to either version when loaded) Most project types will be left entirely untouched though.
It is about Visual Studio 2012 Compatibility
If you created your assets in Visual Studio 2010 with Service Pack 1 (SP1), many of them will load and run in Visual Studio 2012 without any further action on your part.
Many assets will also open again in Visual Studio 2010 with SP1 without any issues, even after you open those assets in Visual Studio 2012
For C++ projects it makes a difference, as the 2012 compiler (VC11) will only be used on projects that are explicitly 2012, not on 2010 projects opened in VS 2012. Some C++11 improvements are available with the VC11 compiler but not with VC10 (see this SO Answer for a summary), including:
Range based for-loops
New standard library headers (atomic, mutex, thread,...)
Smaller standard library container sizes
(And more to follow when the Nov 2012 CTP is delivered to VS 2012)
In order to convert from VS 2010 project to VS2012 there is no need to manually edit the solution file or 'Save As' over the existing project. Instead:
If you decline the update when first prompted, you can update the project later by opening the Project menu and choosing Update VC++ projects... [at the top of the menu options]
From MSDN's "How to: Upgrade Visual C++ Projects to Visual Studio 2012"
(This page was linked from #Joachim's MSDN link, but I wanted to have the answer here on SO since a number of other answers suggested manual workarounds instead of this VS 2012 feature)
In my case, I had some Visual Source Safe stuff (my project was created with Visual Studio 2003/2005, yes, very old!)
Once I manually removed the VSS stuff, the conversion succeeded.
PS: I know it's about VS2010, but maybe this helps others.
You can convert a project from VS2010 to VS2012 by doing the following:
Add the 2010 project to your VS2012 solution by right-click on your solution in the Solution Explorer and Select Add --> Existing Project...
The project will appear in the solution and will have (Visual Studio 2010) appended to its name.
Right-click on the added project and select Properties.
In the Configuration Properties --> General pane, change the setting in Platform Toolset field to Visual Studio 2012 (v110)
Repeat for each configuration type, e.g. Release and Debug.
I came across this question while googling for a solution to a specific problem: MSBuild was failing to execute the Publish target against a VS2012 solution that had started life in VS2010 when called from the command line (specifically through TeamCity):
error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.3\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
MSBuild was looking for the Azure SDK 2.3 targets in the VS10 location (C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.3\Microsoft.WindowsAzure.targets). The cause is explained by Sayed Ibrahim Hashimi in a blog post and, as I understood it, boils down to some decisions they made while enabling cross-version compatibility for solution files. The solution was simple: add the VisualStudioVersion property to the MSBuild invocation, something like this:
msbuild.exe MyAwesomeWeb.sln /p:VisualStudioVersion=11.0
Practically speaking, this overrides the following in each csproj file:
<VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">10.0</VisualStudioVersion>
Presumably you could get the same result by editing all of these by hand to replace 10.0 with 11.0 but that might break backwards-compatibility -- I haven't tried it. I also haven't tried an update to VS2013 to see if the problem persists.
So to wrap this up by answering the question: yes, there are some differences before you "convert" (using any of the methods offered by other answerers) and some differences remain afterwards.
This is slightly different, but along the same lines so in case it helps anyone:
I was loading a project where it looked like it was loading and then kept showing all projects as unavailable. No errors were on the migration report. I tried reloading the solution and projects many times, using various methods including suggestions here.
Finally I found a "Resolve Errors" option when right clicking on the solution in the Solution Explorer. VS went through a load process again and it worked; no problems.
I don't know what it did differently that time, but apparently it made a difference.
it's to simple just edit the .sol file
change the version to 11
like this
Microsoft Visual Studio Solution File, Format Version 12.00
Visual Studio 2012