如何更改Visual Studio 2012安装目录?

时间:2023-01-14 23:44:38

I've uninstalled VS11 using the the windows installer, and deleted just about every registry key I could find relating to it, but it still pops up with this when I try to reinstall it:

我使用windows安装程序卸载了VS11,并删除了几乎所有与它相关的注册表项,但当我试图重新安装它时,它仍然会弹出:

如何更改Visual Studio 2012安装目录?

And I can't click the "..." or edit the path. Right-clicking does nothing either.

我不能点击“…”或编辑路径。右击没有。

What do I have to destroy to change the install directory?

要更改安装目录,需要销毁什么?


Still happening in official release:

仍在官方发布:

如何更改Visual Studio 2012安装目录?

9 个解决方案

#1


48  

I had the same problem though instead of forcing me to install into "c:\program Files" it forced me to install to the directory which I used for the Visual Studio RC. After using Process Monitor and the setup's logfile I was able to find a registry key that needed to be deleted.

我也遇到了同样的问题,它没有强迫我安装到“c:\程序文件”中,而是强迫我安装到我用于Visual Studio RC的目录中。在使用过程监视器和设置的日志文件之后,我能够找到需要删除的注册表项。

The key was located at

钥匙在

HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-21-776561741-789336058-725345543-318838\Components\31F687BD8A467D54C830E018D99F7F3B

微软HKLM \ Software \ \ Windows \ CurrentVersion \安装\用户数据\ s - 1 - 5 - 21 - 776561741 - 789336058 - 776561741 - 318838 \ \ 31 f687bd8a467d54c830e018d99f7f3b组件

The SID will most likely be different for other systems yet you might be able to find the last string (31F687BD8A467D54C830E018D99F7F3B)

对于其他系统,SID很可能是不同的,但是您可能能够找到最后的字符串(31F687BD8A467D54C830E018D99F7F3B)


In order to find the key I did the following:

为了找到钥匙,我做了如下的事:

  1. Downloaded ProcessMonitor from Sysinternals
  2. 下载从Sysinternals ProcessMonitor
  3. Started Processmonitor with filter

    开始Processmonitor过滤器

    Image Path ends with vs_premium.exe

    图像路径以vs_premium.exe结束。

  4. Started vs_premium.exe

    开始vs_premium.exe

  5. Closed the setup
  6. 关闭设置
  7. Waited until Processmonitor didn't fetch anymore events
  8. 直到Processmonitor不再获取事件
  9. Opened the newest dd_vs_premium_.log file from %TEMP%
  10. 打开最新dd_vs_premium_。日志文件从%临时%
  11. Searched for something and found

    找了些东西,找到了

    Condition 'VS_Install_path_KeyExists' evaluated to false. (i guess it will evaluate to true on affected systems. I tried this on a clean windows installation)

    条件'VS_Install_path_KeyExists'计算为false。(我想这对受影响的系统是成立的。我在一个干净的windows安装中尝试过)

  12. One line above it said

    上面一行写着

    Registry key not found. Key = 'SOFTWARE\Microsoft\VisualStudio\SxS\VS7'

    注册表键不见了。关键= '微软软件\ \ VisualStudio \ SxS \ VS7”

  13. Searched for

    寻找

    Microsoft\VisualStudio\SxS\VS7

    微软\ VisualStudio \ SxS \ VS7

    in Processmonitor

    在Processmonitor

  14. A few lines down ProcessMonitor shows me the key I had to delete

    ProcessMonitor下面几行显示了我必须删除的密钥

#2


6  

The only solution I've found is on Windows 7 to create a hard Junction link to the directory your wanting Visual Studio installed to.

我找到的唯一解决方案是在Windows 7上创建一个硬连接链接到要安装Visual Studio的目录。

For Example, My SSD drive is not my boot drive and has a drive letter of B:.

例如,我的SSD驱动器不是我的引导驱动器,并且有一个驱动器B:。

I run the following command line

我运行以下命令行

mklink /J "C:\Program Files (x86)\Microsoft Visual Studio 11.0" "B:\Program Files (x86)\Microsoft Visual Studio 11.0"

"C:\程序文件(x86)\微软Visual Studio 11.0" "B:\程序文件(x86)\微软Visual Studio 11.0"

To the installer and Windows it thinks it installed it to the Program Files x86 directory on C: drive when it really installed it to the Program Files x86 folder on B: drive.

在安装程序和Windows上,它认为它安装在C:驱动器上的程序文件x86目录上,当它真正安装到程序文件x86文件夹的时候,在B:驱动器上。

Here's a link to page about creating Junction links in Windows Vista and 7. http://www.howtogeek.com/howto/windows-vista/using-symlinks-in-windows-vista/

这里有一个关于在Windows Vista和7中创建连接链接的链接。http://www.howtogeek.com/howto/windows-vista/using-symlinks-in-windows-vista/

#3


6  

A simpler approach worked for me:

一种更简单的方法对我起了作用:

1 - Run the installer from the command line, with /uninstall /force switches, as in:

1 -使用/卸载/强制开关从命令行运行安装程序,如下所示:

c:\vs_professional_ENU.exe /uninstall /force

2 - Re-run the installer normally.

2 -重新正常运行安装程序。

I did this with VS2015 under Windows 10. Reference link.

我在Windows 10下做了VS2015。参考链接。

#4


4  

I dont have the rep to comment on the post above. Although he is correct in the syntax of those command switches, the program is bugged, it doesnt work with selecting the CustomInstallPath. In fact, for me, it just decides to open about 50+ iterations of vs_ultimate.exe in the process list...

我没有代表对上面的帖子发表评论。虽然他在这些命令开关的语法上是正确的,但是程序被窃听了,它不能选择CustomInstallPath。事实上,对我来说,它决定打开vs_ultimate的50+迭代。流程列表中的exe…

I will try the Hard Junction as mentioned above as I am sure that will work.

我将尝试上面提到的硬结点,因为我相信它会起作用。

As a sidenote, if anyone is interested, you can use the switch that allows you to acquire the installation ahead of time by running vs_ultimate.exe /Layout X:\somefolder\

作为旁注,如果有人感兴趣,您可以使用允许您通过运行vs_ultimate提前获得安装的开关。exe /布局X:\ somefolder \

I did that last night and hopefully my installation will go quickly since i havea ll the info, however I think in order to force it to use the offline version, you have to run vs_ultimate.exe /noweb.

我昨晚做了,希望我的安装会很快,因为我有很多信息,但是我认为为了迫使它使用离线版本,你必须运行vs_ultimate。exe / noweb。

This page refers to all the switches: http://msdn.microsoft.com/en-us/library/e2h7fzkw(v=vs.110).aspx

这个页面引用了所有的开关:http://msdn.microsoft.com/en-us/library/e2h7fzkw(v=vs.110).aspx

The above pages notes that: /p CustomInstallPath "Installs all re-targetable packages in the directory that you specify." Thay may mean that silently, whatever it is able to install off of your root drive, it will, but its hard to be certain and I have limited space on my SSD.

上面的页面指出:/p CustomInstallPath“在您指定的目录中安装所有可重定向的包。”这可能意味着,不管它能在你的根驱动器上安装什么,它都会,但它很难确定,我的SSD空间有限。

Before I try the hard junction, I may also try the above and see what heppens, then uninstall it if need be. Will post results

在我尝试硬连接之前,我也可以尝试一下上面的内容,看看heppens是什么,如果需要,可以卸载它。将结果

#5


2  

Try launching the installer with the following option:

尝试使用以下选项启动安装程序:

/p CustomInstallPath="[your_path]"

For example:

例如:

vs_ultimate.exe /p CustomInstallPath="C:\MyDirectory"

To see all options use the switch /?

要查看所有选项,请使用开关/?

#6


2  

How to change Visual Studio 2012 install directory? What do I have to destroy to change the install directory?

如何更改Visual Studio 2012安装目录?要更改安装目录,需要销毁什么?

Answer: You can change the physical directory without the need to "destroy or change" the install directory. This is an alternative "think smarter not harder" solution proposal.

答:您可以更改物理目录,而不需要“销毁或更改”安装目录。这是另一种“想得更聪明而不是更困难”的解决方案。

Here are the specific material details you need to continue to use your logical M:\Program Files directory and solve the physical where the files are stored problem.

这里是您需要继续使用您的逻辑M:\程序文件目录并解决文件存储的物理问题的具体材料细节。

It also serves the rest of the community well for cleaner more reproducible installs, less effort and risk when using Beta builds. Its less risk because it encapsulates every file in the beta install. Want to go from beta to RC, no problem, just don't mount the beta drives, use an off the shell registry cleaner and reinstall clean to fresh drives every time.

在使用Beta版本时,它也为社区的其他成员提供了更好的可再生安装、更少的工作量和风险。它的风险更小,因为它封装了beta安装中的每个文件。想要从beta到RC,没问题,只是不要安装beta驱动器,使用shell注册表清理器,每次重新安装干净的驱动器。

The process uses PGP disks which can be logged in and logged out of / backed up as needed.

该过程使用PGP磁盘,可以根据需要登录和注销/备份。

Initially, it seemed as though it would be possible to create just two drives. not so. - Drive #1 mounted as F:\ for f:\Program Files (x86)\Microsoft Visual Studio 11.0 This is where I told Visual Studio setup to install files to. And it does function as a mountable container for 2.7 Gigs of files.

最初,似乎只可能创建两个驱动器。不是这样的。-驱动器1安装为F:\程序文件(x86)\Microsoft Visual Studio 11.0这是我告诉Visual Studio setup要安装文件到的地方。它可以作为2.7 g文件的可挂载容器。

  • Drive #2 mounted as a folder on "C:\Program Files (x86)\" "Microsoft Visual Studio 11.0" The intended purpose of the mounted folder was to collect up the remainder of 5.5 Gigs of files.
  • 驱动#2安装在“C:\程序文件(x86)\”“Microsoft Visual Studio 11.0”的文件夹中,安装的文件夹的预期目的是收集剩下的5.5 gb文件。

The actual list of 33 created folders I had to move to additional PGP folders.

我必须将创建的33个文件夹的实际列表移到附加的PGP文件夹中。

Here is the inclusive list of folders you can create before setup deploys files to them.

这是在安装程序将文件部署到文件夹之前可以创建的文件夹列表。

C:\Program Files\Microsoft SQL Server
C:\Program Files\Microsoft SQL Server Compact Edition
C:\Program Files\Application Verifier
C:\Program Files\MSBuild
C:\Program Files\Microsoft
C:\Program Files\IIS Express
C:\Program Files\IIS
C:\Program Files\Microsoft Visual Studio 11.0

C:\Program Files (x86)\IIS
C:\Program Files (x86)\IIS Express

C:\Program Files (x86)\Microsoft ASP.NET
C:\Program Files (x86)\Microsoft Help Viewer
C:\Program Files (x86)\Microsoft SDKs
C:\Program Files (x86)\Microsoft SQL Server
C:\Program Files (x86)\Microsoft SQL Server Compact Edition
C:\Program Files (x86)\Microsoft WCF Data Services
C:\Program Files (x86)\Microsoft Web Tools
C:\Program Files (x86)\MSBuild
C:\Program Files (x86)\NuGet
C:\Program Files (x86)\Windows Kits

C:\Program Files (x86)\Common Files\Merge Modules
C:\Program Files (x86)\Common Files\Microsoft
C:\Program Files (x86)\Common Files\microsoft shared\DevServer
C:\Program Files (x86)\Common Files\microsoft shared\MSDesigners8
C:\Program Files (x86)\Common Files\microsoft shared\MSEnv
C:\Program Files (x86)\Common Files\microsoft shared\MSI Tools
C:\Program Files (x86)\Common Files\microsoft shared\SQL Debugging
C:\Program Files (x86)\Common Files\microsoft shared\SQL Server Developer Tools
C:\Program Files (x86)\Common Files\microsoft shared\TextTemplating
C:\Program Files (x86)\Common Files\microsoft shared\Visual Database Tools
C:\Program Files (x86)\Common Files\microsoft shared\VS7Debug
C:\Program Files (x86)\Common Files\microsoft shared\WF
C:\Program Files (x86)\Common Files\microsoft shared\Windows Simulator

This is perfect to prevent; - Patch managers and patch management systems which inadvertently & unsupervised unmonitored, unaudited in willful ignorant bliss violate the premise of good promotion to production change control best practices

这是完全可以预防的;-补丁管理和补丁管理系统在不经意间和无人监督的情况下未被监控,未经审计的故意的无知的极乐,违反了良好的推广到生产变更控制最佳实践的前提。

  • Developers who's code mostly works by random chance and really have no idea whats in the final product.

    开发人员的代码大部分是随机工作的,他们真的不知道最终的产品是什么。

  • Hacker exploitation of the build environment.

    黑客对构建环境的利用。

Could have used True Crypt or PGP desktop. Just not whole disk encryption, have to be able to mount and unmount the resources.

可以使用真正的Crypt或PGP桌面。只是不是整个磁盘加密,必须能够安装和卸载资源。

I appreciate the hard junction approach, but unless you Safely ejecting & power off drives, it offers little process compliance and is neither safe or reliable as compared to safe PGP un-mounting/mounting. Developers will just power on the drives and make changes.

我很欣赏这种硬连接方式,但是除非您安全地弹出和关闭驱动器,否则它提供很少的过程遵从性,而且与安全的PGP未安装/安装相比,它既不安全也不可靠。开发人员只会对驱动进行驱动并进行更改。

Regarding level of efforts to backup and restore, Backing up PGP drives as compared to hard junctioned drives is a wash about the same level of effort. But the value in not having to remember which folders are junctioned, which might need restored to restore a dev environment favors the fewer number of .PGD drives which contain all the needed folders ( ie do the remembering for you as a part of their function)

关于备份和恢复的工作级别,备份PGP驱动器与硬盘连接驱动器相比,需要花费相同的精力。但是不需要记住哪些文件夹是连接的,哪些可能需要恢复以恢复开发环境,这样做的价值在于,包含所有所需文件夹的.PGD驱动器的数量更少(即作为函数的一部分为您记忆)

Consider this as an environment for when requirements are for mandatory non discretionary absolute auditable surety for a reproducible secure build. To meet that core objective, it has to be available only when its actually "needed" and has to be secured when its not needed.

考虑到这是一个环境,当需求是强制性的,非*裁量的绝对可审计的,可重复的安全构建的保证。为了实现这一核心目标,它必须只有在实际“需要”时才可用,并且必须在不需要时加以保护。

#7


1  

For me the final visual studio 2012 wanted to install into the same path as the (uninstalled) beta. I deleted most of the stuff in HKLM that had an exact match for the setup directory (ending with a \ e.g. C:\VS11Beta\) and then the setup let me choose again.

对我来说,最终的visual studio 2012想要安装到(未安装的)beta的相同路径中。我删除了HKLM中与设置目录完全匹配的大部分内容(以C:\VS11Beta\结尾),然后设置让我再次选择。

Probably not a solution for the OP(M:\Program Files sounds too generic to delete), but perhaps for others with this problem.

可能不是OP的解决方案(M:\程序文件听起来太通用了,不能删除),但是对于有这个问题的其他人来说可能是这样。

#8


1  

I had previously installed the VS 2012 Test Controller. Uninstalling it allowed me to change the install path.

我之前安装过VS 2012测试控制器。卸载它允许我更改安装路径。

#9


0  

Look into your installed programs and see if an instance of Visual Studio is already installed if so delete it and re-run the set up.

查看已安装的程序,如果已经安装了Visual Studio实例,请删除它并重新运行设置。

#1


48  

I had the same problem though instead of forcing me to install into "c:\program Files" it forced me to install to the directory which I used for the Visual Studio RC. After using Process Monitor and the setup's logfile I was able to find a registry key that needed to be deleted.

我也遇到了同样的问题,它没有强迫我安装到“c:\程序文件”中,而是强迫我安装到我用于Visual Studio RC的目录中。在使用过程监视器和设置的日志文件之后,我能够找到需要删除的注册表项。

The key was located at

钥匙在

HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-21-776561741-789336058-725345543-318838\Components\31F687BD8A467D54C830E018D99F7F3B

微软HKLM \ Software \ \ Windows \ CurrentVersion \安装\用户数据\ s - 1 - 5 - 21 - 776561741 - 789336058 - 776561741 - 318838 \ \ 31 f687bd8a467d54c830e018d99f7f3b组件

The SID will most likely be different for other systems yet you might be able to find the last string (31F687BD8A467D54C830E018D99F7F3B)

对于其他系统,SID很可能是不同的,但是您可能能够找到最后的字符串(31F687BD8A467D54C830E018D99F7F3B)


In order to find the key I did the following:

为了找到钥匙,我做了如下的事:

  1. Downloaded ProcessMonitor from Sysinternals
  2. 下载从Sysinternals ProcessMonitor
  3. Started Processmonitor with filter

    开始Processmonitor过滤器

    Image Path ends with vs_premium.exe

    图像路径以vs_premium.exe结束。

  4. Started vs_premium.exe

    开始vs_premium.exe

  5. Closed the setup
  6. 关闭设置
  7. Waited until Processmonitor didn't fetch anymore events
  8. 直到Processmonitor不再获取事件
  9. Opened the newest dd_vs_premium_.log file from %TEMP%
  10. 打开最新dd_vs_premium_。日志文件从%临时%
  11. Searched for something and found

    找了些东西,找到了

    Condition 'VS_Install_path_KeyExists' evaluated to false. (i guess it will evaluate to true on affected systems. I tried this on a clean windows installation)

    条件'VS_Install_path_KeyExists'计算为false。(我想这对受影响的系统是成立的。我在一个干净的windows安装中尝试过)

  12. One line above it said

    上面一行写着

    Registry key not found. Key = 'SOFTWARE\Microsoft\VisualStudio\SxS\VS7'

    注册表键不见了。关键= '微软软件\ \ VisualStudio \ SxS \ VS7”

  13. Searched for

    寻找

    Microsoft\VisualStudio\SxS\VS7

    微软\ VisualStudio \ SxS \ VS7

    in Processmonitor

    在Processmonitor

  14. A few lines down ProcessMonitor shows me the key I had to delete

    ProcessMonitor下面几行显示了我必须删除的密钥

#2


6  

The only solution I've found is on Windows 7 to create a hard Junction link to the directory your wanting Visual Studio installed to.

我找到的唯一解决方案是在Windows 7上创建一个硬连接链接到要安装Visual Studio的目录。

For Example, My SSD drive is not my boot drive and has a drive letter of B:.

例如,我的SSD驱动器不是我的引导驱动器,并且有一个驱动器B:。

I run the following command line

我运行以下命令行

mklink /J "C:\Program Files (x86)\Microsoft Visual Studio 11.0" "B:\Program Files (x86)\Microsoft Visual Studio 11.0"

"C:\程序文件(x86)\微软Visual Studio 11.0" "B:\程序文件(x86)\微软Visual Studio 11.0"

To the installer and Windows it thinks it installed it to the Program Files x86 directory on C: drive when it really installed it to the Program Files x86 folder on B: drive.

在安装程序和Windows上,它认为它安装在C:驱动器上的程序文件x86目录上,当它真正安装到程序文件x86文件夹的时候,在B:驱动器上。

Here's a link to page about creating Junction links in Windows Vista and 7. http://www.howtogeek.com/howto/windows-vista/using-symlinks-in-windows-vista/

这里有一个关于在Windows Vista和7中创建连接链接的链接。http://www.howtogeek.com/howto/windows-vista/using-symlinks-in-windows-vista/

#3


6  

A simpler approach worked for me:

一种更简单的方法对我起了作用:

1 - Run the installer from the command line, with /uninstall /force switches, as in:

1 -使用/卸载/强制开关从命令行运行安装程序,如下所示:

c:\vs_professional_ENU.exe /uninstall /force

2 - Re-run the installer normally.

2 -重新正常运行安装程序。

I did this with VS2015 under Windows 10. Reference link.

我在Windows 10下做了VS2015。参考链接。

#4


4  

I dont have the rep to comment on the post above. Although he is correct in the syntax of those command switches, the program is bugged, it doesnt work with selecting the CustomInstallPath. In fact, for me, it just decides to open about 50+ iterations of vs_ultimate.exe in the process list...

我没有代表对上面的帖子发表评论。虽然他在这些命令开关的语法上是正确的,但是程序被窃听了,它不能选择CustomInstallPath。事实上,对我来说,它决定打开vs_ultimate的50+迭代。流程列表中的exe…

I will try the Hard Junction as mentioned above as I am sure that will work.

我将尝试上面提到的硬结点,因为我相信它会起作用。

As a sidenote, if anyone is interested, you can use the switch that allows you to acquire the installation ahead of time by running vs_ultimate.exe /Layout X:\somefolder\

作为旁注,如果有人感兴趣,您可以使用允许您通过运行vs_ultimate提前获得安装的开关。exe /布局X:\ somefolder \

I did that last night and hopefully my installation will go quickly since i havea ll the info, however I think in order to force it to use the offline version, you have to run vs_ultimate.exe /noweb.

我昨晚做了,希望我的安装会很快,因为我有很多信息,但是我认为为了迫使它使用离线版本,你必须运行vs_ultimate。exe / noweb。

This page refers to all the switches: http://msdn.microsoft.com/en-us/library/e2h7fzkw(v=vs.110).aspx

这个页面引用了所有的开关:http://msdn.microsoft.com/en-us/library/e2h7fzkw(v=vs.110).aspx

The above pages notes that: /p CustomInstallPath "Installs all re-targetable packages in the directory that you specify." Thay may mean that silently, whatever it is able to install off of your root drive, it will, but its hard to be certain and I have limited space on my SSD.

上面的页面指出:/p CustomInstallPath“在您指定的目录中安装所有可重定向的包。”这可能意味着,不管它能在你的根驱动器上安装什么,它都会,但它很难确定,我的SSD空间有限。

Before I try the hard junction, I may also try the above and see what heppens, then uninstall it if need be. Will post results

在我尝试硬连接之前,我也可以尝试一下上面的内容,看看heppens是什么,如果需要,可以卸载它。将结果

#5


2  

Try launching the installer with the following option:

尝试使用以下选项启动安装程序:

/p CustomInstallPath="[your_path]"

For example:

例如:

vs_ultimate.exe /p CustomInstallPath="C:\MyDirectory"

To see all options use the switch /?

要查看所有选项,请使用开关/?

#6


2  

How to change Visual Studio 2012 install directory? What do I have to destroy to change the install directory?

如何更改Visual Studio 2012安装目录?要更改安装目录,需要销毁什么?

Answer: You can change the physical directory without the need to "destroy or change" the install directory. This is an alternative "think smarter not harder" solution proposal.

答:您可以更改物理目录,而不需要“销毁或更改”安装目录。这是另一种“想得更聪明而不是更困难”的解决方案。

Here are the specific material details you need to continue to use your logical M:\Program Files directory and solve the physical where the files are stored problem.

这里是您需要继续使用您的逻辑M:\程序文件目录并解决文件存储的物理问题的具体材料细节。

It also serves the rest of the community well for cleaner more reproducible installs, less effort and risk when using Beta builds. Its less risk because it encapsulates every file in the beta install. Want to go from beta to RC, no problem, just don't mount the beta drives, use an off the shell registry cleaner and reinstall clean to fresh drives every time.

在使用Beta版本时,它也为社区的其他成员提供了更好的可再生安装、更少的工作量和风险。它的风险更小,因为它封装了beta安装中的每个文件。想要从beta到RC,没问题,只是不要安装beta驱动器,使用shell注册表清理器,每次重新安装干净的驱动器。

The process uses PGP disks which can be logged in and logged out of / backed up as needed.

该过程使用PGP磁盘,可以根据需要登录和注销/备份。

Initially, it seemed as though it would be possible to create just two drives. not so. - Drive #1 mounted as F:\ for f:\Program Files (x86)\Microsoft Visual Studio 11.0 This is where I told Visual Studio setup to install files to. And it does function as a mountable container for 2.7 Gigs of files.

最初,似乎只可能创建两个驱动器。不是这样的。-驱动器1安装为F:\程序文件(x86)\Microsoft Visual Studio 11.0这是我告诉Visual Studio setup要安装文件到的地方。它可以作为2.7 g文件的可挂载容器。

  • Drive #2 mounted as a folder on "C:\Program Files (x86)\" "Microsoft Visual Studio 11.0" The intended purpose of the mounted folder was to collect up the remainder of 5.5 Gigs of files.
  • 驱动#2安装在“C:\程序文件(x86)\”“Microsoft Visual Studio 11.0”的文件夹中,安装的文件夹的预期目的是收集剩下的5.5 gb文件。

The actual list of 33 created folders I had to move to additional PGP folders.

我必须将创建的33个文件夹的实际列表移到附加的PGP文件夹中。

Here is the inclusive list of folders you can create before setup deploys files to them.

这是在安装程序将文件部署到文件夹之前可以创建的文件夹列表。

C:\Program Files\Microsoft SQL Server
C:\Program Files\Microsoft SQL Server Compact Edition
C:\Program Files\Application Verifier
C:\Program Files\MSBuild
C:\Program Files\Microsoft
C:\Program Files\IIS Express
C:\Program Files\IIS
C:\Program Files\Microsoft Visual Studio 11.0

C:\Program Files (x86)\IIS
C:\Program Files (x86)\IIS Express

C:\Program Files (x86)\Microsoft ASP.NET
C:\Program Files (x86)\Microsoft Help Viewer
C:\Program Files (x86)\Microsoft SDKs
C:\Program Files (x86)\Microsoft SQL Server
C:\Program Files (x86)\Microsoft SQL Server Compact Edition
C:\Program Files (x86)\Microsoft WCF Data Services
C:\Program Files (x86)\Microsoft Web Tools
C:\Program Files (x86)\MSBuild
C:\Program Files (x86)\NuGet
C:\Program Files (x86)\Windows Kits

C:\Program Files (x86)\Common Files\Merge Modules
C:\Program Files (x86)\Common Files\Microsoft
C:\Program Files (x86)\Common Files\microsoft shared\DevServer
C:\Program Files (x86)\Common Files\microsoft shared\MSDesigners8
C:\Program Files (x86)\Common Files\microsoft shared\MSEnv
C:\Program Files (x86)\Common Files\microsoft shared\MSI Tools
C:\Program Files (x86)\Common Files\microsoft shared\SQL Debugging
C:\Program Files (x86)\Common Files\microsoft shared\SQL Server Developer Tools
C:\Program Files (x86)\Common Files\microsoft shared\TextTemplating
C:\Program Files (x86)\Common Files\microsoft shared\Visual Database Tools
C:\Program Files (x86)\Common Files\microsoft shared\VS7Debug
C:\Program Files (x86)\Common Files\microsoft shared\WF
C:\Program Files (x86)\Common Files\microsoft shared\Windows Simulator

This is perfect to prevent; - Patch managers and patch management systems which inadvertently & unsupervised unmonitored, unaudited in willful ignorant bliss violate the premise of good promotion to production change control best practices

这是完全可以预防的;-补丁管理和补丁管理系统在不经意间和无人监督的情况下未被监控,未经审计的故意的无知的极乐,违反了良好的推广到生产变更控制最佳实践的前提。

  • Developers who's code mostly works by random chance and really have no idea whats in the final product.

    开发人员的代码大部分是随机工作的,他们真的不知道最终的产品是什么。

  • Hacker exploitation of the build environment.

    黑客对构建环境的利用。

Could have used True Crypt or PGP desktop. Just not whole disk encryption, have to be able to mount and unmount the resources.

可以使用真正的Crypt或PGP桌面。只是不是整个磁盘加密,必须能够安装和卸载资源。

I appreciate the hard junction approach, but unless you Safely ejecting & power off drives, it offers little process compliance and is neither safe or reliable as compared to safe PGP un-mounting/mounting. Developers will just power on the drives and make changes.

我很欣赏这种硬连接方式,但是除非您安全地弹出和关闭驱动器,否则它提供很少的过程遵从性,而且与安全的PGP未安装/安装相比,它既不安全也不可靠。开发人员只会对驱动进行驱动并进行更改。

Regarding level of efforts to backup and restore, Backing up PGP drives as compared to hard junctioned drives is a wash about the same level of effort. But the value in not having to remember which folders are junctioned, which might need restored to restore a dev environment favors the fewer number of .PGD drives which contain all the needed folders ( ie do the remembering for you as a part of their function)

关于备份和恢复的工作级别,备份PGP驱动器与硬盘连接驱动器相比,需要花费相同的精力。但是不需要记住哪些文件夹是连接的,哪些可能需要恢复以恢复开发环境,这样做的价值在于,包含所有所需文件夹的.PGD驱动器的数量更少(即作为函数的一部分为您记忆)

Consider this as an environment for when requirements are for mandatory non discretionary absolute auditable surety for a reproducible secure build. To meet that core objective, it has to be available only when its actually "needed" and has to be secured when its not needed.

考虑到这是一个环境,当需求是强制性的,非*裁量的绝对可审计的,可重复的安全构建的保证。为了实现这一核心目标,它必须只有在实际“需要”时才可用,并且必须在不需要时加以保护。

#7


1  

For me the final visual studio 2012 wanted to install into the same path as the (uninstalled) beta. I deleted most of the stuff in HKLM that had an exact match for the setup directory (ending with a \ e.g. C:\VS11Beta\) and then the setup let me choose again.

对我来说,最终的visual studio 2012想要安装到(未安装的)beta的相同路径中。我删除了HKLM中与设置目录完全匹配的大部分内容(以C:\VS11Beta\结尾),然后设置让我再次选择。

Probably not a solution for the OP(M:\Program Files sounds too generic to delete), but perhaps for others with this problem.

可能不是OP的解决方案(M:\程序文件听起来太通用了,不能删除),但是对于有这个问题的其他人来说可能是这样。

#8


1  

I had previously installed the VS 2012 Test Controller. Uninstalling it allowed me to change the install path.

我之前安装过VS 2012测试控制器。卸载它允许我更改安装路径。

#9


0  

Look into your installed programs and see if an instance of Visual Studio is already installed if so delete it and re-run the set up.

查看已安装的程序,如果已经安装了Visual Studio实例,请删除它并重新运行设置。