分类: Windows

Windows 上统一管理代理环境变量（HTTP_PROXY / HTTPS_PROXY / NO_PROXY）

目标：在 Windows PowerShell 5.1、PowerShell 7、Git Bash 中，按需自动设置代理，并避免 VPN/内网地址被误代理

1. 背景与坑位总结

1.1 环境变量代理是什么？

很多命令行工具会读取以下环境变量来决定是否走 HTTP 代理：

• HTTP_PROXY / HTTPS_PROXY（大写）
• http_proxy / https_proxy（小写）
• NO_PROXY / no_proxy：指定哪些地址 不走代理（非常关键，防止 VPN 内网被代理坑死）

1.2 大小写有什么区别？哪个“正确”？

没有“唯一正确”，只有“兼容性”：

• Linux/macOS 生态传统更常用小写 http_proxy
• Windows/企业工具更常见大写 HTTP_PROXY
• 很多程序两者都支持，但并非全部

✅ 最稳做法：
- 在 Bash（Git Bash/WSL）：大写 + 小写都设置
- 在 PowerShell/Windows：大写优先，必要时也补小写

1.3 为什么一定要配 NO_PROXY？

否则会出现经典现象：

• VPN 内网能 ping
• 但浏览器/HTTPS 不通、curl 握手失败、jumpserver 打不开

典型需要 bypass 的范围：
- localhost, 127.0.0.1
- 192.168.0.0/16（家庭/公司内网常见）
- 10.0.0.0/8
- 172.16.0.0/12

继续阅读

Troubleshooting MSBuild Publish Issues on Servers with Visual Studio Build Tools

Introduction

When deploying .NET Framework web applications (such as those using Sitecore Helix) on a production or build server, you might encounter a frustrating issue: MSBuild runs successfully with 0 errors, but no files are output to the specified publish directory. This problem often arises when using the minimal Visual Studio Build Tools installation, as opposed to a full Visual Studio IDE setup on a development machine. In this blog post, I'll walk through the symptoms, root cause, and step-by-step resolution based on a real-world scenario. This guide assumes you're working with a .NET Framework 4.8 web project and MSBuild commands for publishing to a file system.

The goal is to make your build server "publish-ready" without installing the full Visual Studio IDE, which is unnecessary (and resource-heavy) on servers.

Symptoms of the Issue

• MSBuild Command Execution: You run a command like this:
  

  MSBuild.exe "C:\path\to\YourProject.csproj" /restore /p:Configuration=debug /p:DeployOnBuild=True /p:PublishProfile=Local /p:WebPublishMethod=FileSystem /p:PublishUrl="C:\path\to\publish\folder" /p:TransformConfigFiles=true /p:IncludeSetAclProviderOnDestination=False /v:detailed
  
  

  • It completes with 0 errors (possibly many warnings, e.g., 429 in some cases).
  • Logs show property reassignments, framework path searches, and successful builds of dependencies, but no mention of actual publishing (e.g., no execution of WebPublish targets).

继续阅读

Installing Windows 7 Desktop Gadgets and System Monitor II on Windows 11

References

https://www.majorgeeks.com/files/details/system_monitor_ii.html
https://winaero.com/windows-7-desktop-gadgets-for-windows-11/
https://web.archive.org/web/20220427233938/https://winaero.com/windows-7-desktop-gadgets-for-windows-11/

Windows 7 Desktop Gadgets were a beloved feature for many users, offering quick access to tools like calendars, clocks, and system monitors. While Microsoft removed this feature starting with Windows 8, you can bring these gadgets back to Windows 11 using the Gadgets Revived package and enhance your desktop with additional tools like System Monitor II. This blog post walks you through the process of installing Windows 7 Desktop Gadgets and the System Monitor II gadget on Windows 11.

Prerequisites

• A Windows 11 PC (e.g., running build 22H2 or later).
• Internet access to download the required files.
• Administrative privileges to install software.

继续阅读