I tried to install Visual Studio 2012 . but it showing me "Unable to locate package source" I can select "Download from the internet" or "Provide a location to search for the packages" And this is path that comes up:
C:\Users\JA\Download\packages\vcRuntimeDebug_amd64\cab1.cab
(the 'packages' folder does not exists) When I select to download from the internet its showing up again after some time, I searched for "vcRuntimeDebug_amd64" folder but it doesn't contain "cab1.cab" file ;/
Note please, that i runned setup file as administrator and i disable firewall .
I had the same problem but with Windows Phone 8 SDK. I tried several things (which are detailed below, in my previous answer), and the best option was to download the ISO, found in the Install Instructions section:
http://www.microsoft.com/download/details.aspx?id=35471
After finishing, it said it couldn't download that runtime, but at least the emulator is running fine. I guess you could manually download that runtime
afterwards if you have any problems. Here's the link:
http://www.microsoft.com/download/details.aspx?id=30679
Previous attempts:
I downloaded the Visual C++ Redistributable for Visual Studio 2012 Update 4 to see if that way the installer skipped that step, but it didn't work.
Then I looked for cab1.cab in my disk and found it in several folders, being this one the one that worked:
C:\ProgramData\Package Cache\{CF2BEA3C-26EA-32F8-AA9B-331F7E34BA97}v11.0.61030\packages\vcRuntimeMinimum_amd64
Of course that GUID will be different in your case, so you should look for a vcRuntimeMinimum_amd64 folder.
Inside that folder was not only the cab1.cab but also a vc_runtimeMinimum_x64.msi file. When I told the installer to use that folder, it still didn't work. Then I chose "Browse" but when I opened that folder it didn't show any file because the installer was looking for vcRuntimeMinimum_x64 (without the underscore). I typed "." in the textbox so it showed all the files, I chose vc_runtimeMinimum_x64.msi and the installation continued. It took a while but it worked.
Later I had the same issue with sdk_tools35res.cab. I told the installer to use v3.11.50727\packages\sdk_tools35res\sdk_tools35res.msi and the process continued.
But in the end, I got three errors: Tools for .Net 3.5, MS VC++ runtime and .NET 4.5 SDK. So then I decided to download the ISO.
Related
I've just downloaded and installed Android Studio but there is no Android submenu in Tools menu and no AVD Manager icon on the instrument panel. When I start SDK Manager, there is an error message:
Please specify a Android SDK location
SDK Manager screenshot: "Please specify a Android SDK location"
If I click on Edit link next to Android SDK Location field, there is another error message:
Your SDK location contains non-ASCII characters
SDK Components Setup screenshot: "Your SDK location contains non-ASCII characters"
I studied these somewhat similar questions, but non of them helped me:
Your project path contains non-ASCII characters android studio
Unable to install SDK tools component while installing Android Studio
unable to install or locate android sdk in android studio
NO Android option in "tool" menu, and no avd manager
I see that the path really contains non-ASCII characters, but is there any workaround other than uninstall Android Studio and then install it from scratch to some other directory like С:\Android\SDK?
UPD:
it seems there is no such workaround at this time
As a matter of fact at the moment there is no other way than to re-install Android Studio to some other directory with no non-ASCII characters and blank spaces, like С:\Android\SDK
I guess you've solved this by now but I ran into the same problem today and after a little research and some annoying tries I solved it. What I found out is this:
Using mklink function you can create a junction to a location but it will not boter if you are creating a it to a non existing location(that's the "file not found" you were getting). And you are creating a junction to a non existing location in this case due to C:\Users\username\AppData\Local\Android\Sdk should(not sure about this) be created by the Android Studio Setup Wizard during installation. In order to solve that, you should create \Android\Sdk in C:\Users\username\AppData\Local and it's done.
The installer does not show junctions to non existing locations in the Sdk install location so if you don't create the folders you can't select the link.
Finally but not less important, the installer does not allow the Sdk to be installed in a folder in the root directory C:\, so you have to create the junction in any other directory but the root one or move it if it's already there(that's what I did).
As I was writting this the installer was running and when it was done I came across the exact same problem with the location to store Android Proyects, and so the same solution to the installer must be aplied to the Save location in the New proyect step.
This is exactly what I did:
1) Create \Android\Sdk in C:\Users\username\AppData\Local\
2) Open cmd as admin and enter the following command:
mklink /J "C:\..\android-sdk" "C:\Users\username\AppData\Local\Android\Sdk"
It will return this:
C:\WINDOWS\system32>Junction created for C:\..\android-sdk <<===>> C:\Users\username\AppData\Local\Android\Sdk
Note: android-sdk is the name the junction will have, you can name it as you like and \..\ reffers to the folder where you want to put the it in, make sure there are no non-ASCII characters in the folder's name anyways.
3) In the Sdk install location, select C:\..\android-sdk and the installation will be ready to go.
4) Repeat the process for the Save location for new proyects, just instead of C:\Users\username\AppData\Local\Android\Sdk use the location you want the proyects to be stored in.
Didn't try moving the junctions files but I suggest you don't, I guess that could get the paths lost and mess up the installation.
Hope this is usefull and good luck with your proyects!
If you don’t want to reinstall the Android SDK in another location you can also create a junction point which is a link to the actual location. You can use the junction tool to do this.
For example, you can create the directory C:\Android and then create the junction SDK and claim the SDK lives there with
Junction C:\Android\SDK C:\Users\Whatever\actual\location
The operating system will show the same contents under both paths and applications will not know the difference.
Hey I had the same problem here but I was able to fix it by just changing the directory to a new folder directly on the hard drive.
Hope this can help.
In my case since I have a Windows 10 operating system, and my sdk was located in Program Files. Having spaces in the directory caused some sort of error, to solve this I used mklink to create a junction called android-sdk in the C drive that pointed at the directory where my sdk was located.
If you can't find the sdk in
C:\Users\username\AppData\Local\Android\Sdk
I suggest looking at
C:\Program Files (x86)\Android\android-sdk
then trying
mklink /J "C:\android-sdk" "C:\Program Files (x86)\Android\android-sdk"
Afterwards open Android Studio go to Project Defaults > Project Structure > Android SDK, click on the "..." button to browse for your sdk and select the junction you just created. Or if you still haven't setup android studio because of this issue, open the application as administrator select the theme settings and all that, and when you reach the setup sdk section, click on the "..." button to browse for your sdk and select the junction you just created.
Important to run Android Studio setup as administrator otherwise you may experience issues downloading components, if you still have issues it might be your antivirus blocking the setup.
I have a several (c#) solutions (originally created with VS2012) that include portable libraries that I have trouble opening with VS2013. Some of them fail to open with
Unsupported This version of Visual Studio is unable to open the
following projects. The project types may not be installed or this
version of Visual Studio may not support them.
The problem only happens on my home environment. At work or on other setups everything works as expected.
To get it to work on my home environment, I have to right-click on the projects and choose "Edit Project.csproj ..." from the context menu for any project that was not loaded correctly. If all projects are open as text files in VS, I close the solution and reopen it again. Now, the projects failed to open, since VS is unable to open a project in two different modes (as a project vs as a text file). If you choose now "reload" from the context menu, the project loads correctly.
I can now close the solutions, and if I am lucky, eveything works after I reopen it again.
After some time, some of the projects fail to load. Then, I try to do the edit/reload trick again, but when I reload the solution, other portable projects are doomed. So, I have no choice but to start over (deleting the suo file takes me back to square-one, all portable projects are unable to load).
Any idea what I have screwed up with my system? I have installed all service packs and extensions. I also have the newest resharper version installed.
Update:
Not sure if it is related but I just got the following compiler warning for one of the incompatible projects
Warning 1 The element 'PropertyGroup' in namespace
'http://schemas.microsoft.com/developer/msbuild/2003' has invalid child element
'MinimumVisualStudioVersion' in namespace
'http://schemas.microsoft.com/developer/msbuild/2003'. List of possible elements
expected: 'Property, .... Project.csproj 1
Update 2:
VS Output window shows The application for the project is not installed. for all those projects that cannot be loaded. "Repairing" VS did not help, I will try to do a clean reinstall now.
I'm trying to install Visual Studio 2012 Express for Windows Desktop and every time I run the installer I get this error:
"Windows Program Compatibility mode is on. Turn it off and then try setup again."
I checked the file properties and compatibility mode was off. Googling found that changing the name to "vs_premium.exe" or "vs_ultimate.exe" or changing the registry keys might help, but the name changes had no effect, and there were no registry keys to delete. I have restarted my machine several times to no avail.
Changing to Visual Studio 2013 is not an option for me, as my work computer has Visual Studio 2012 on it which they will not update to 2013, and I need to work on my project on both computers.
The computer I am using has a Windows 8.1 HP Pavilion g6. I have installed Visual Studio 2013 for Windows Desktop, Web, and Windows, as well as the 30-day trial for Professional (which has recently expired). I have also installed Visual Studio 2012 for Windows Phone but I have not used it yet.
Previous posts are correct in that compatibility mode appears to be based entirely on file names. There is a simple method for determining precisely which name Windows expects:
Right-click the file, select Properties and navigate to the Details tab. There should be an entry labelled "Original filename". Simply rename the file accordingly and it should run happily.
Screenshot:
If you downloaded Visual Studio 2012 and Visual Studio 2013 at the same time and one was renamed with a "(0)" suffix (just as I did) then change the installer to the original name will probably fix it, because "somehow compatibility checking is based on file naming"
I just have to Rename the setup name. I rename the setup file to vs_ultimate and it worked.
In case you mounted it, first extract the content before you install. it worked for me.
Had the same issue installing vs_ultimate on Windows 10, It tells me to turn compatibility mode off which I didn't know to do. After reading all the solutions above without success, I was able to solve it on my own.
I mounted the .iso before installing which was giving me problem, but later as I extracted it into a desktop folder, it installed fine.
I couldn't find a solution, but I could find a workaround. I downloaded the offline installer (ISO) and ran that instead. It's not a solution, but it should work in this situation.
I ran into this problem and the solution for me was to rename the file back to its original name. I had downloaded it as "vs2012sdk_full.exe" but the original name was "vssdk_full.exe". When I ran it as "vs2012sdk_full.exe" I got the compatibility mode error. Once I renamed it back to the original "vssdk_full.exe" it worked.
Open The Run (Win+R) And type Services.msc.
Found Program Compatibility Assistant Service Then Disable Service and Stop it.
Open the Run (Win+R) And Type Gpedit.msc.
User configuration-->Administrative Templates-->Windows Components-->Application Compatibility
And check Enable button then restart system.
Run as administrator. And for my 2013 installer I renamed it to be
vs_professional.exe
And it worked.
In a round about way I discovered the problem on my system. Check the properties of the installer. Mine was blocked because it was downloaded from another system. Click unblock. Voila! If you can't find the location of the installer, run it again. When it fails, leave it running. Open task manager, right click the installer, then open file location. This will take you to the folder containing your installer.
mount the ISO file and run the setup as a from the disk.
I had the same issue, my solution was to run it in administrator mode and it seemed to work just fine.
Run as Administrator worked for me.
I had the same problem. I had run the installer from an ISO, reading from the DVD image.
The solution was to simply take the ISO and uncompress it as a .RAR into some folder, and everything worked.
Well, filename varies from versions to versions. Fix:
Right Click on file
Select Properties
Select "Details" tab
Rename that file to value of "Original Filename"
This is the solution:
Right Click on Visual Studio Setup Icon
Select Properties
Open Compatibility Tab
Check Run This Program In Compatibility Mode
Select Your Windows Version (ex:Windows 8)
Finally Click OK And Install Your Program Again
I have Visual Studio 2012 Ultimate and I've downloaded the Visual Studio 2012 ISO from MSDN.
When trying to install the documentation:
I open Visual Studio as an Administrator
Follow these instructions as per the install's ReadMe file
On the menu bar for Visual Studio 2012, choose Help, Add and Remove
Help Content.
Help Viewer 2.0 starts, showing the Manage Content tab.
On the Manage Content tab, choose the Disk option button, choose the
Browse (…) button, and then navigate to the DVD drive.
Choose the helpcontentsetup.msha file, and then choose the Open button.
Under Available Documentation, the list of available content sets from the
DVD appears.
Choose the Add link next to the content set that you want
to install onto your local computer.
The items that you specify appear
in the Pending Changes column. You can remove an item from the Pending
Changes column by choosing the “X” next to the item.
Choose the Update button.
And click Update.
When I click Update, it progresses for about 3-4 seconds, and then it fails with an error:
The following errors occurred while performing the requested tasks:
An error occurred while updating content. You have insufficient
privileges to complete this task.
How can I resolve this issue?
Update
I'm running Help Viewer in Admin mode.
try this. It solved my problem.
change security permission of vs2012doc.iso to full control for your account.
Mount it
Install the documentation ONE BY ONE. Remember ONE BY ONE.
Might it help...
Change your machine date and try again. In my case work with "oct/01/2012".
This was using the Visual Studio 2013 but is likely to be similar to the help of Visual Studio 2012 and probably 2015. I have not tried it so you tell me.
I got the ISO with the help of vs2013 to Microsoft directly. Now I do not remember the address so I did not put it here. It is very easy to get around with google looking for.
When I'm using the Microsoft Help Viewer 2.1 with local installation way I get an error: Insufficient Privileges and not the books are installed.
What I will describe is possible for you to do so more easily. But I could not validate it and then they describe the steps I followed to do so.
The first thing I did was copy the entire contents of the ISO to a folder on my HDD for my comfort my case was in C:\T
With the command prompt navigate to the folder where it was copied from the iso content and the C:\T\Packagesrun the following winrar t * .cab
This causes a test winrar make all cab files and protest whenever any of them is corrupt.
This was to score those files that had to go down again, in my case only had a .cab file with problems
v2Visual_Studio_2011_NET_Framework_4_B1545_VS_100_en-us_13(b0ba5cce-2b72-f582-80f3-8a6165ef6b9b).cab
The following was download it directly from Microsoft in this direction,
http://packages.mtps.microsoft.com/v2Visual_Studio_2011_NET_Framework_4_B1545_VS_100_en-us_13(b0ba5cce-2b72-f582-80f3-8a6165ef6b9b).cab
All other packages I think are there too.
The next thing was to replace the damaged file with the new and final step is to go into the folder where the files of the Visual Studio Help are, in my case I always use to put this folder in a comfortable place for me.
D:\VS_2012_2013_HLP\VisualStudio12
Inside this folder there are other two \Incoming\Cab, we must ensure that the cab folder is completely empty.
The last thing is to enter the Microsoft Help Viewer 2.1 and say that the new power plant is one where we copy the contents of the ISO (D:\T\helpcontentsetup.msha). The rest is just install the books ..
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