Is there anyway to downloangrade visual studio extensions. Visual Studio Extension keep the older version or not. if not where can i find the older version of extensions.
i'm trying to downgrade VS10X Extension to 3.68 or 3.67 version
Thanks
Unless you have downloaded the visx file with the preovious version this is not possible via VS gallery. Contact the package owner - btw, release 3.69 is now available.
Related
Unfortunately I have updated my Android studio to 3.2.4 and since then, many issues occured.
I read from the 0.57 Changelog
Android tooling has been updated to match newer configuration
requirements (SDK 27, gradle 4.4, and support library 27); building
with Android plugin 3.2 doesn't work due to the gradle scripts, so
please stay on Android Studio 3.1 for now
Now I can neither downgrade nor download version 3.1.
Old versions are available in Android Studio download archives.
I have Visual Studio 2013 with update 3 installed.
On the first time i opened my project, it prompted me to download and install
Azure SDK 2.2 and so i did.
When i tried to build, it fails and gives me this error message:
Error 109 WAT080 : Failed to locate the Windows Azure SDK. Please make sure the Windows Azure SDK v2.1 is installed.
So I installed SDK 2.1 but the build still fails with the same error.
These are my installed azure SDKs: 2.1, 2.2, 2.3, 2.4.
I also confirmed that the folders of each version are NOT missing here:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Windows Azure Tools
We started the cloud project which is an MVC site on the 3rd quarter of 2013 when the Windows Azure 2.2 released and I had no problem.
Is it possible that these Azure SDKs are conflicting?
It's fixed now. Unfortunately, you cannot find the Azure SDK 2.2 for VS 2013 and older versions in web platform installer anymore. So you have to manually install all the components (according to version).
I noticed that this folder is missing.
C:\Program Files\Microsoft SDKs\Windows Azure.NET SDK\v2.2
Which means that WindowsAzureLibsForNet-x64.msi is not yet installed.
You can download it here: http://www.microsoft.com/en-us/download/details.aspx?id=40893.
I've seen solved threads about this but the solution didn't solve for everyone. I hope this would help.
I had to restart Visual Studio after Azure SDK install. ServiceHostingSDKBinDir was set fine in msbuild, but not in the VS.
I added C:\Program Files\Microsoft SDKs\Windows Azure.NET SDK\v2.3 (or whatever sdk you need eg. 2.2, 2.4) to the system path and it fixed the issue of VS2013 not being able to find the SDK.
After I'd changed the system path, I had to restart VS2013.
I use Visual Studio 2012 and this is the only version of Visual Studio I have installed. I need to build certain C++ projects with the v90 platform toolset (of Visual Studio 2008), but I can't install Visual Studio 2008.
I understand it is possible to use the v90 platform toolset by installing Windows SDK 7.0. How exactly is it done? If I simply use the web installer of 7.0 SP1, I still don't see v90 as one of the possible platform toolsets.
It is possible, but apparently requires some maneuvering and will not support building MFC applications. The following assumes that VS2012 update 4 is installed, but neither VS2010 nor VS2008 are installed.
Download the x86 DVD of SDK 7.0 SP1 (GRMSDK_EN_DVD.iso). Mount the ISO or extract its contents, and manually install the MSI files from the following folders under the Setup folder:
WinSDK (this may fail, it's ok)
WinSDKBuild
WinSDKInterop
WinSDKTools
WinSDKWin32Tools
vc_stdx86
vc_stdamd64
winsdk_intellidocs
WinSDKIntellisenceRefAssys
WinSDKNetFxTools
Download the x86 DVD of SDK 7.1 (GRMSDK_EN_DVD.iso). Mount the ISO or extract its contents, and manually install the MSI files from the same folders listed above (except winsdk_intellidocs, which doesn't exist).
Go to C:\Program Files (x86)\Microsoft Visual Studio 9.0. Copy the following files from Common7\IDE to VC\bin:
msobj80.dll
mspdb80.dll
mspdbcore.dll
mspdbsrv.exe
Now you should be able to choose the v90 platform toolset in Visual Studio 2012 and build with it.
Explanations (and sources):
Individual MSI installation is based on the second workaround from this connect report.
The requirement for both 7.0 and 7.1 is based on this question (both VS2010 and VS2008 are required to use v90 in VS2012!). SDK 7.1 is not needed if you have VS2010.
DLL/EXE copying requirement is based on yet another question. If you do not copy them, you will see error MSB6006: "CL.exe" exited with code -1073741515.
In addition to this answer I want to add that
You can install SDK 7.0 simply by running setup, there is no problem with it.
You can install SDK 7.1 by running setup, if you remove Microsoft Visual C++ 2010 Redistributables first and fix following registry values:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client]
"Version"="4.0.30319"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full]
"Version"="4.0.30319"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4\Client]
"Version"="4.0.30319"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4\Full]
"Version"="4.0.30319"
You can (and probably should) restore these values to whatever they originally were after installation is complete.
Do not forget to install KB2519277 after this, it updates compilers in SDK 7.1 to SP1.
You don't need to copy any dll. MSBuild uses
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VC#ProductDir
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\9.0\Setup\VC#ProductDir
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VS#ProductDir
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\9.0\Setup\VS#ProductDir
to set up paths. It's probably wise to fix them to point to "C:\\Program Files (x86)\\Microsoft Visual Studio 9.0\\VC\\" and "C:\\Program Files (x86)\\Microsoft Visual Studio 9.0\\" as it might be useful elsewhere in build process.
Same goes for version 10.0 if you plan to use Windows7.1SDK toolset.
Use WindowsSdkVer.exe to set current SDK to 7.1 to defeat cryptic error in Microsoft.Cpp.x64.Targets(63,5) about missing unnamed required file. If the tool gives you error, then set these values manually:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows#CurrentInstallFolder
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows#CurrentInstallFolder
to point to newly installed SDK. The tool needs some registry keys from Visual Studio installation to work properly, but there are many and I'm not sure which are important.
Reboot. None of the above asks you to, but without reboot I got errors when trying to build a project.
As an aside, SDK7.1 adds v100 toolset, but it won't work, saying something about Could not find WindowsSDKDir variable from the registry. This is because v100 actually requires SDK7.0A which comes with Visual Studio 2010 and is not available separately. Windows7.1SDK toolset is the one which utilises VC2010 compilers if you need them.
Microsoft.Cpp.Win32.*.props files have a lot of relevant stuff if something fails in build system.
One addition/update for VS2013 to Yodans answer:
My working setup:
VS2013 has to use VS2010 libs
Using WinSDK 7.1 (Yodans 2.) build tools (v100) in VS2013
clean install, uninstalling everything mentioned in the sdk release notes (can be downloaded at http://www.microsoft.com/en-us/download/details.aspx?id=8279 under category Details)
Microsoft Windows SDK for Windows 7 (7.1) (the Windows SDK core-component files)
Application Verifier
Debugging Tools for Windows
Windows Performance Toolkit
Microsoft Help Viewer 1.0
Microsoft Visual C++ 2010 Redistributable
Microsoft Visual C++ 2010 Standard Edition
Additionally removed all .NET and VC++ related MS Software (not tested if necessary)
choosing Windows7.1SDK as Platform Toolset in VS2013
error MSB6006: "CL.exe" exited with code -1073741515
cl.exe uses msobj100.dll, mspdb100.dll, mspdbcore.dll and mspdbsrv.exe
Added to PATH C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
Build works and binary is usable ( So now its tested Yodan ;-) )
My mistake:
copied files in 7. above to C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin (Yodans 3.), believing this dir is in PATH, but it was not!
So better do as sugested by Yodan and tested by myself in 8. above
p.s. same answer is solving this problem:
Visual Studio 2013: CL.exe exited with code -1073741515
I am trying to make a windows 8 application using Visual Studio 2012. Its an RSS reader and i am using Split App - Javascript template. When i build the app i am getting this warning :
Warning : DEP0810 : This app references Microsoft.WinJS.1.0, version 1.0.8514.0, found in your SDK, but you have a higher version of Microsoft.WinJS.1.0 installed on the target machine, 1.0.9200.20602. If you continue to run this application, it will run against the currently installed version, Microsoft.WinJS.1.0, version 1.0.9200.20602. Consider updating your SDK to match the version of Microsoft.WinJS.1.0 that is installed.
I don't know how to update the SDK.
Any help is appreciated.
Try downloading the latest version of the 'Visual Studio 2012 Extensions for the Windows Library for JavaScript', below:
http://www.microsoft.com/en-us/download/details.aspx?id=30687
I had a similar problem with Visual Studio 2013 and MS WinJS.2.0 which I updated from the following web address which resolved the problem:
http://www.microsoft.com/en-gb/download/details.aspx?id=40793
We have a Visual Studio solution that contains some VC++ projects, and we've currently upgraded to Visual Studio 2012 from VS2010. In the process we also lifted the VC++ projects to PlatformToolset v110.
On our build server (Jenkins), we would like to build this project with MsBuild without having to install VS2012. But I can't get it to work, and I think it's because the folder C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110 must be present.
This folder and its contents is created during installation of VS2012, but as far as I can tell it won't be included in either the Windows SDK 7.1 or Windows SDK 8.0?
Is there any other SDK or installation package that can help with this issue?
I know it's not really without installing Visual Studio 2012, but:
If licensing costs are the biggest driver perhaps the Express for Windows Desktop edition could be an alternative. You could keep the installation to the minimum required to support C++ builds.