如何移动构建输出临时文件位置 [英] How to move build output temp file location

查看:73
本文介绍了如何移动构建输出临时文件位置的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

大家好,

我们正在公司测试Windows Applocker,以防止用户在c:\users \ usernamename个人资料目录中运行exes,脚本等。

We're testing Windows Applocker at my company to prevent users running exes,scripts etc in their c:\users\username profile directory.

Visual Studio 2017专业版显然使用c:\\​​\\users\username \ appdata \ local \ temp \来转储随机命名的cmd文件,然后将其作为一部分执行部署。所以这与我们试图通过Applocker完成的工作完全相反。

Visual Studio 2017 pro is apparently using c:\users\username\appdata\local\temp\ to dump randomly named cmd files and then execute them as part of deployment. So that's directly in opposition to what we're trying to accomplish with Applocker.

要解决这个问题,显然我们想要更改VS用于这些cmd文件的输出目录。部署,我搜索了很多,还没有找到一个允许我这样做的设置。从字面上看,VS正在使用来自用户环境变量的%TEMP%

To work around this, clearly we'd like to change the output directory VS is using for these cmd files during deployment, and I've searched quite a bit and have not yet found a setting that will allow me to do that. It literally looks like VS is using %TEMP% from the user environment variable.

有谁知道如何更改它?

谢谢

推荐答案

Visual Studio的用户不需要这样保姆。考虑到他们可以在%USERPROFILE%之外的任何可写位置下创建任何可执行文件或脚本,然后运行它。

Users of Visual Studio do not need to be nannied this way. Consider that they can make any executable or script under any writable location, outside of %USERPROFILE%, and run that.

- pa


这篇关于如何移动构建输出临时文件位置的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆