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.
Related
I've been trying to install VSCommunity Edition for the last few hours with no luck. If you check the screenshot attached. You'll see that I can change the directories for installation for the first 2 requirements, but im unable to change the directory for the 3rd option (the SDK install along with others) which just happen to be the very large percentage of files. It's wanting to install over 45gb of files on my C Drive which is just a 50gb SSD.
enter image description herehttps://i.imgur.com/burFR90.jpg
I want to switch to D, and the only thing i can see fro any of the Microsoft help docs and posts is "You can change this upon fresh installation".
Which this is. I've uninstalled anything else remotely like it just to be sure.
Do any of you have any ideas or any experience with this issue, or anything i can try? I simply don't have enough space to install on C, and because of this, i can't start learning c# which is required for work.
Thanks so much in advance guys, it's really getting me worried now.
Although I can only guess why Visual Studio is locking down the SDK path, here's a few workarounds and recommendations:
In your screenshot, the installer warns you about possible performance effects of installing Visual Studio on your D drive. I assume this is because your D drive is not an SSD. Microsoft's Visual Studio system requirements document recommends that you install to an SSD, and based on community experience, this is one recommendation you really want to stick to, otherwise IDE responsiveness may be well below your expectations, especially if you decide to install extensions in future.
Instead, you might want to reconsider the set of components that you're installing. If you're only getting started with C#, you'll probably be just fine with developing class libraries, console and web applications targeting .NET Framework or .NET Core. If this is the case, you might want to go to the Workloads tab in the installer and opt out of some of the heaviest workloads (such as Mobile development with .NET). Consider only installing .NET desktop development, ASP.NET and web development, Azure development and .NET Core cross-platform development. If you only select these, your installation is going to be much slimmer.
If minimizing Visual Studio installation as shown above isn't enough, consider an alternative way of setting up your .NET development environment. For example, you can download and install .NET Core SDK and .NET Core Runtime, and use one of the two most prominent alternative code editors: Visual Studio Code or JetBrains Rider that are both quite compact.
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 VS 2013 Professional in Windows 10 and the installation is stuck at one step or the other every single time (Eg: At one time, it was stuck forever saying "Applying Visual Studio Core Features", at other times it gets stuck at "Build x86 Runtime").
Bottom line is, I tried killing the installation several times (may be atleast 20 times already) in the past 4 days and reinstall. Every single time, the installation is stuck at one or the other step. Acquiring section is showing 100 %. Applying section gets stuck in the middle.
I had VS 2013 Ultimate in Windows 8.1 (prior to that VS 2012 Express for Web and Windows).
This is driving me crazy, I even reimaged my Windows 10 and cleaned the registry using ccCleaner and stuff. Nothing, literally nothing works when it comes to installing VS2013 (or 2012 or 2015 - I tried different versions and different editions).
Please help.
Had the same issue when installing on a virtual machine WS2008R2.
When looking at resource monitor i noticed my physical memory was all used up. Hardly any available / free.
I first started by killing all processes that i knew weren't necessary for the install which ended up not being enough, so i disabled my anti-virus. It took a while for my AV to unload it's memory but it eventually was able to move onto the next step(s) of the installation.
This is obviously on a different OS but i'm curious if you're having the same issues and your machine just simply doesn't have enough available resources to perform the tasks at hand.
Give it a shot and let me know if it helps!
I really want to upgrade to Visual Studio 2010. But since I do a lot of development for the Pocket PC version of Windows Mobile I cannot. (I develop for a Symbol device that does not support Windows Phone 7, so that is not a option.)
Does any one know any kind of time frame of when Microsoft plans to add support for Smart Device Projects into Visual Studio 2010?
Update: Since this is looking less and less likely without intervention from the users, Please go here and vote for this feature.
Microsoft's current public statement says that, apart from Windows Phone 7 development, there will not be Smart Device Application Development added to Visual Studio 2010.
This obviously raises concerns and has implications for a lot of people, and there are more than a few of us lobbying Microsoft very hard to change that plan and to get them to include some sort of support for Smart Device programming outside of Windows Phone.
I'm hopeful, maybe even optimistic, that their stance will change and that we will get something - even if it's only CF 3.5 targeting actual hardware (i.e. no emulator support) - at some point down the road. Right now they've got all hands on deck trying to get Windows Phone out the door, and until that happens, I wouldn't expect much for resource allocation toward other device features.
So what does that actually mean? In my mind I wouldn't postpone installing VS2010 until they have device support. My guess is it won't happen until early next year at the absolute earliest and realistically I would say mid to late next year if it happens at all. Again, I'm optimistic that it will, but I'm also a realist, so I'm not going to base my business decisions and future on it happening.
Add your support to the following Microsoft Connect Item, it's had quite a bit of interest being the 3rd highest voted suggestion so far.
http://connect.microsoft.com/VisualStudio/feedback/details/595712/no-support-for-windows-ce-and-compact-framework-development-in-vs2010
Through private conversations I've had with the Customer Advocacy Team at MS it would appear that they are really digging their heels in over this. MS reneged on promises to include Smart Device Framework support in VS2010 early on in the product life cycle.
It is really frustrating because at some point the development tools will fragment and you'll end up with having to maintain separate development, source control and build systems for targeting Windows CE. Who is to say that the tools will even work on future versions of Windows either or even if they will live side by side with future versions of VS. Remember this lack of support also hurts people doing unmanaged code on CE too.
MS is doing a great job of remaining silent here, the silence is already causing people to look at alternative platforms. Without a statement of intent no business is going to invest in Windows CE development without knowing the future of the OS and the tools to develop on it.
All recent Visual Studio versions can be installed side by side. You could upgrade now for desktop development, then when smart device support is rolled out, migrate your projects to VS2010.
http://social.msdn.microsoft.com/Forums/en/setupprerelease/thread/fce95ec7-728d-41d1-ab13-74a2fd3a4136
I am forced to have two VS installations side by side. However, another issue - that is causing me more pain is that TFS 2010 doesn't work with VS 2008 - there is a plugin, of course, but there are many issues with it which make it unusable.
So to have source control, I have installed SVN on my machine.
Microsoft once again, has proven that they have no concern for the devs at all. Their tools don't work together, backward compatibility is not there, all of which makes their dev tools a big load of crap.
MS replied to that connect issue:
Hi folks,
In the first quarter of 2013, we plan to provide tooling for Visual
Studio 2012 to create apps for Windows Embedded Compact v.Next. We’ll
be announcing more details in September, including the roadmap for
.NET CF. You can find more details this Fall in the Windows Embedded
Compact website at http://www.windowsembedded.com.
thanks, Doug Turnure Visual Studio PM
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.