A couple of months back, most probably in November last year, I had to install Microsoft Visual Studio on a drive(D) other than C because my C drive did not have enough space to host the software. Two weeks ago I cleaned up my C drive and now I want to move the Visual Studio installation to the C drive because the C drive is located on an SSD drive, and the other drives are on HDD.
The Microsoft Official Document reference says that I have to reinstall my Visual Studio. But always there are some exceptional experiences for the users other than the official documentation statements.
One very important cause for my avoiding this reinstallation is, that I live in such a corner of the globe where 30GB will take me like 3 to 4 days to download. Moreover, it will also hamper regular tasks and the custom settings and tweaks I have applied to my development environment.
That's why I am writing this to avail community help if anyone has ever experienced such an issue and solved it anyhow.
I have a 120Gb SSD (C:) and a 1Tb HD (D:). Because of that I installed VS 2017 on D, but as I install workloads, it goes to C, and I don't have the space for that. I researched and found nothing, so here am I. Someone knows how to change the install location of these workflows?
Edit: I already changed the Android SDK folder.
I'm trying to run appcelerator studio in my Desktop.
AMD Athlon II x4 640 3.00 GHz
Ram 4gb
64bit win 8.1
120Gb SSD Samsung 840 EVO
so, in my laptop i7 8gb ram etc.. run smoothly.
When I'm trying to start the studio doesn't respond, not even in task manager.
I'm using CLI and work fine..
I can't find any log file. Which appc studio keep in workspace which one I have no create yet because I can't open the studio.
I run the command appc platform to start the studio from the CMD but nothing happens and this message appears:
{"success":false,"description":"platform command usage: appcelerator platform <api> <method/arguments>"}
I uninstalled AVAST and check first the blocked programs, but nothing..
I disabled Windows firewall too.
Reinstalled the studio many times using different versions of node. But nothing.
And of course I tried to come in contact with the appc team but I can't....
I'm thinking about 4Gb ram limitation; if that blocks the program from starting.
I also try to open the program logged in and logout from CLI.
Any idea? any one with the same problem?
I am not stuck in loading screen the studio try to verify my account and communicate with server.
Studio just won't start at all.
I'm sorry for my bad English.
sorry for your issue.
First - I am assuming your running Windows (Linux is no longer supported)
The CLI command your using appc platform does not launch studio. That is used for accessing platform APIs and thus requires you to provide an API to use.
To launch studio from the CMD line on Windows you would need to cd into your Appcelerator Studio directory and run the associated program. When installing studio, we do put an icon on the desktop, which is by far the easiest way to start it up.
Your right about your RAM limitation. While you'll find that studio does "run" it will be extremely slow, especially once you start using the Android / Windows emulators etc. Windows takes up 1-2GB of Ram on its own, leaving very little for any development tools.
Our recommended configuration for Windows machines is:
* Windows 8.1 or higher
* 16GB of RAM
I would also think about a faster proc as well.
We are in the process of updating our documentation on the pre-reqs' as its a bit misleading. While we say 4GB of RAM is suitable, what we are talking about is 4GB of 'free memory' on top of everything else you have running, not 4GB of total system memory.
I will be getting another pc where drive C: will be SSD and the rest of the drives HDD. The SSD size is significantly smaller so I don't want it to get full from just codes and Visual Studio stuff.
I came across this guide:
http://www.placona.co.uk/1196/dotnet/installing-visual-studio-on-a-different-drive/
but at the bottom, it says that it's not a permanent solution because updates will still get installed in drive C:
I haven't tried this yet but:
does the latest version of visual studio allow you to install on another drive?
would it be better if I create a VM (on another drive) then install Visual Studio there? any downside on developing while in a VM?
I am trying to install VS2008 sp1 to my work machine - it has a pathetic 10Gb C drive. The SP1 bootstrapper doesn't give the option to install items to D, only C. It needs 3Gb free and the machine only has about 700Mb.
VS allowed me to install to D originally why not the SP. The only thing I can think of that it requires system files installed in Windows etc, but I can't believe there are 3Gb worth of system files?
Worth a read:
http://blogs.msdn.com/heaths/archive/2008/07/24/why-windows-installer-may-require-so-much-disk-space.aspx
I was faced with the same problem, and ended up moving my Outlook archive.pst and the windows.edb (the new live search index file) over to D: to make room instead of trying to cram a square peg into a round hole with SP1 splitting drives. A huge help in this regard is WinDirStat, which scans a drive of your choice and identifies the size of every folder and file so that you can reveal some random large entities and move them if you can.
If you have an empty partition, you can try to create a mounted drive (i.e. map the partition to an empty folder on the C: drive) and see whether the SP1 bootstrapper will be able to use it.
I also ran into the same problem on a server that only has 20gb on the C: drive. I found a way to free up enough space to get the job done by reassigned the system's virtual memory allocation to use D: drive instead of C:. This freed up about 4gb in my case.
On Windows XP the place to set this is in My Computer system properties, Advanced tab, Performance Options:
http://support.microsoft.com/kb/308417
I had the same problem with VS2008 installed on a C: drive that was only 12Gb in size.
I uninstalled VS2008 completely by following the manual steps in this page,
and then by using the auto-uninstaller:
http://msdn.microsoft.com/en-us/vstudio/bb968856.aspx
I then rebooted the machine.
I then re-installed VS2008 on the E: drive.
I then rebooted the machine.
I was then able to install SP1 - as now it did not need quite as much space on C: drive.
When you say "10Gb C drive", do you mean it's a 10-gig disk or a partition? If the former, you should really be looking at replacing the drive - it's old, and I'd be starting to worry about how much longer it has to live.
If the latter, then assuming that the C: drive restriction can't easily be worked around, then I'd look at increasing the size of the C: partition. Depending on how full the remainder of the drive is, this can take a while. I'd also be considering spending some tens of dollars ($40 or $50, I'd guess) on a partition manager from someone such as Acronis or Paragon. Kick it off just before you finish work for the day - it may take several hours, especially if the disk's fairly full.
Are you in place upgrading your current version or have you uninstalled VS 2008 Gold? By default, the installer won't let you change the directory if any existing versions of VS are installed.
To move the installation, you will need to uninstall all editions of 2008 you have installed (including any Express Editions) and then the choose installation location option should enable.
I vaguely recall having this happen to me when I had Office 2007 installed first before VS 2008. I don't remember what options that I had installed for Office 2007.
Update: I remember now it had to do with the fact that I had Visual Studio Tools for Office already installed. When I upgraded my computer I did a clean install of everything without problems by installing VS 2008 before installing Office 2007 and VSTO. So most likely you have to uninstall whatever is causing VS 2008 to want to go to a specific drive.
Even if you do get it to switch drives it still is going to put a lot of stuff on the system drive.
You could also download the full VS2008 SP1 ISO image from here.
Then you can either burn it to DVD or use a tool such as Virtual CD-ROM Control Panel from Microsoft to mount the ISO as another drive.
After mounting the ISO as a virtual drive, you can run the SP1 install from there.