I've been using VS 2013 for a while and now I have installed VS 2012 due to a project requirement. I'm using Qt, with this project, and there seems to be a problem where Qt can't find stddef.h. When investigating into the problem I noticed that the problem comes from VCInstallDir pointing to the wrong location (It points E:\Program Files(x86)\Visual Studio.... while the actual install is at C:\Program Files(x86)\Visual Studio). What I did was I found all entries in the registry that points to the E:\path\to\VS and converted them to C:\path\to\VS. Now, I restart Windows and create a Qt project again and still VCInstallDir points to the wrong location. I can't figure out where VS 2012 is reading this value from. Could someone kindly point out as to how I can override this value?
Related
I am trying to build a Xamarin.iOS(runtime v4.0.30319) project but keep getting the following error
Severity Code Description Project File Line Suppression State
Error Can not resolve reference: /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS/Facades/System.Threading.Tasks.Extensions.dll myApp.iOS C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets 795
When I look in C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\ReferenceAssemblies\Microsoft\Framework\Xamarin.iOS\v1.0\Facades I can see System.Threading.Tasks.Extensions.dll exists.
and when I compare Xamarin.iOS.Common.targets on another machine that works, there are no differences
after extensive searching I have not been able find a solution. I have also tried:
manually adding the .dll to the iOS project
reinstalling the .netstandard framework which is used
deleting the solution and pulling from source control (I'm the only one affected by this issue)
compared my set up to other working set ups
Extra information (possibly irrelevant): This is a cross platform solution and when built in the android environment, everything works as expected.
This issue was caused by a versioning mismatch.
I was running developing in on my windows machine and deploying to an iOS device via a mac on my local network.
The iOS version held on the mac differed from the version in my xamarin iOS project (the mac had been updated by another dev).
The resolution for me was to make sure both versions were the same
I too had a similar problem but there was no System.Threading.Tasks.Extensions.dll on the Mac in the /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS/Facades folder. However on the Windows PC, this file exists in the C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\ReferenceAssemblies\Microsoft\Framework\Xamarin.iOS\v1.0\Facades folder.
The solution for me was to copy the System.Threading.Tasks.Extensions.dll file from the Windows PC to the Mac.
I ran into this issue as well. My solution was to launch Visual Studio on the Mac (in my case a Mac Mini) and grab all updates for Visual Studio. One of the updates specifically mentioned the System.Threading.Tasks.Extensions.dll issue that I had been experiencing. After the updates I was able to build the project.
Release note of Visual Studio 15.9.4 :
"Error MT2002: Failed to resolve 'System.Runtime.CompilerServices.AsyncValueTaskMethodBuilder' reference from 'System.Threading.Tasks.Extensions...'" when building a Xamarin.iOS project."
https://learn.microsoft.com/fr-fr/visualstudio/releasenotes/vs2017-relnotes#-visual-studio-2017-version-1594visual-studio-2017-version-1594-
Below is the error that I is displayed when in tried to run Orchard (1.10 and 1.10.1) source from Visual studio 2015 community version.
I know that it is somehow related with configuration settings, but I am unable to solve it.
The same files, when placed in the local IIS runs without any problems. Is there anything that I am missing in visual studio 2015?
How to resolve this error?
Is the displayed 'Config file' path corresponding to your folder?
Because it doesn't seem to be a folder coming from the source code.
Sometime, IIS Express messes up when you try to launch a site with the same port that a previously used one.
Try to read your applicationhost.config (see IIS Express in tasks bar to get the path).
You could also try to change the port in Orchard.Web properties.
I'm trying to run an SSIS package in Visual Studio 2012. When I click the "Start" button I get this very odd error in a popup from Visual Studio:
Method not found: 'Boolean
Microsoft.SqlServer.Dts.Design.VisualStudio2012Utils.IsVisualStudio2012ProInstalled()'.
(Microsoft.DataTransformationServices.VsIntegration)
Clicking on the show technical information, I get this stack trace:
===================================
Failed to start project (Microsoft Visual Studio)
===================================
Method not found: 'Boolean Microsoft.SqlServer.Dts.Design.VisualStudio2012Utils.IsVisualStudio2012ProInstalled()'. (Microsoft.DataTransformationServices.VsIntegration)
------------------------------
Program Location:
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.LaunchVsDebugger(IVsDebugger iVsDebugger, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.ValidateAndRunDebugger(Int32 flags, IOutputWindow outputWindow, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, ProjectItem startupProjItem, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchActivePackage(Int32 launchOptions)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.Launch(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
Has anyone ever seen this error before or know what the issue might be? A bit of googling turned up absolutely nothing for me.
I was able to happily develop and run SSIS packages from Visual Studio 2012 without any issues just a couple days ago (I did reboot my PC over the weekend and some windows updates were installed)
ETA:
I was able to find a couple very recent technet posts about this here and here so I suspect this was something that broke in an update over the weekend. One post says he solved the issue by reinstalling, but of course I'd rather not go that route if I don't have to.
Open the Developer Command Prompt for VS212 as Administrator
execute the command cd "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies"
execute the command gacutil /if Microsoft.SqlServer.Dts.Design.dll
restart Visual Studio
Source msdn Fail to start project
For visual Studio 2013 execute the command cd "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\PrivateAssemblies" in point 2 and then execute point 3 and 4.
The following is the command we have to use to resolve the issue:
"C:\Program Files\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools\gacutil.exe" /if "C:\Program Files\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies\Microsoft.SqlServer.Dts.Design.dll"
Make sure that your dll file and Gacutil.exe file locations are correct. It may be different in other systems.
Note: You should open your “Command Prompt” as an administrator to run the above command.
I experienced the same problem.
Downloaded and installed SQL Server 2012 SP2 and that seemed to have fixed the problem.
Hope this helps!!
This is probably happening because you have Visual Studio 2013 and the BI tools for it installed also. If you use Visual Studio 2013 for the same package it will probably work. The other answer suggesting the run of gacutil to register the old version may have negative impacts later when you want to use the Visual Studio 2013 tools for SSIS.
I had the exact same thing just happen and miraculously now my machine has been "fixed".
(I actually had it happen on both a Win 8.1 machine and a new Win 7 machine.)
My colleague and I noticed that the SSIS toolbox was missing from my IDE. After opening an SSIS package, going to the SSIS menu, and adding back in my "SSIS Toolbox", for some strange reason, my packages now run fine.
I'm guessing a recent update reset the behavior of the IDE.?.?
If this black magic worked for me, I'm hoping it will work for others.
EDIT:
I had the behavior revert itself.
I uninstalled SQL Server 2012 SP2 HF 5522, then rebooted
I then uninstalled SQL Server 2012 SP2, then rebooted
After that, my IDE still gave the error.
I then tried to apply SQL Server SP1 CU 9, but my environment said it wasn't needed.
I then rebooted one last time.
My SSIS Packages run again.
Voodoo...
If you're running across this issue somewhat after the fact (as I did), it appears that it has been fixed in a later release of the SSDT-BI tools installer. Either that, or the process of re-installing fixed it for me.
The file name of the installer on the download page has not changed, but there was a new version released in March of 2015. The new version number is 11.0.5583.0, and the previous version that was causing this error was 11.0.3436.0.
So a simple update might be sufficient. It worked for me with no changes to the GAC.
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 am developing a command line application that creates a full Visual Studio 11 solution made of a single VC++ project and that tries to compile it in the end using MSBuild.
The problem I am facing is strange.
If I execute my command line program inside Visual Studio 11 it works; if I instead launch it outside the development environment it throws me the error:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.Targets(511,5): error MSB8008: Specified platform toolset (v110) is not installed or invalid. Please make sure that a supported PlatformToolset value is selected. [f:\ABC.vcxproj]
The command I am using is the following:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe f:\snake\W9A30040.vcxproj /property:PlatformToolset=v110;Configuration=Debug /v:quiet
But I have the feeling that PlatformToolset=v110 is ignored and MSBuild use v100 (Visual Studio 2010).
Do you have any suggestions how to tell MSBuild to compile for v110 Platform Toolset?
I ran into the same problem as well with the full release of VS 2012. You can also set the VisualStudioVersion as a property with MSBuild as opposed to dealing with environment variables as mentioned in the accepted answer. For instance:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe .\myproject.vcxproj /p:VisualStudioVersion=11.0
The environment variables approach I'm sure work just as well, I honestly didn't try that as I was trying to stay away from having to modify the environment variables.
Make sure that the top of your .SLN file looks like this:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2012
When you double-click on the solution file, it's the # Visual Studio 2012 that controls which version of Visual Studio is loaded (and controls the icon displayed in Windows Explorer).
However, when you run MSBuild, it looks at the Format Version 12.00 part.
Confused?
This is confusing, since Visual Studio 2010 is version 10.0 and Visual Studio 2012 is version 11.0 (not 12.0), and using the version 12.0 solution file format causes MSBuild to (implicitly) set VisualStudioVersion to 11.0.
I found a workaround for this issue; could be a problem of Visual Studio 11 Beta that will be resolved before official release.
Anyway, if you are interestedm just set the environment variable "VisualStudioVersion" equal to "11.0" before calling MSBuild.exe.
In batch files
set VisualStudioVersion=11.0
or in VB.NET
Environment.SetEnvironmentVariable("VisualStudioVersion", "11.0")
Starting with Visual Studio 2013, MSBuild is now part of Visual Studio, and the correct path should be $(MSBuildToolsPath) (“C:\Program Files (x86)\MSBuild\12.0\Bin”). If you use msbuild.exe from the .Net framework folder (“C:\Windows\Microsoft.NET\Framework64\v4.0.30319”) it will not able to distinguish the vs2012 and vs2013 versions.
Use the menu based options to do this. From VC++2010 Express:
- Right click on the main file of the project (not the solution itself at the very top of the tree).
- Click General.
- Find Platform Toolset on the right side of the dialog, top half.
- Change from v110 to v100.
- Click OK.
----- Done ------
Microsoft provides a batch file to set all the EnvVars
You find it in the Start Menu under "Microsoft Visual Studio 2012/Visual Studio Tools" or in the Visual Studio folder ("C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\VsDevCmd.bat")