向Visual Studio.NET 2002中添加生成前和生成后操作

We have VS.NET2002 a project that hasn't been updated to VS.NET2003 and logisitically can't for a few weeks.  However, we had a need for a post-build file copy.  It's a large Online Banking project (since we do eBanking here at Corillian) for a very large Financial Institution, so there's lots of people working on the project at once.  Ordinarily the project is built with the increasingly snazzy NAnt so these post-build processes are no biggie.  However, sometimes you'd just like to do stuff from VS.NET. 

我们有VS.NET2002一个项目，该项目尚未更新到VS.NET2003，并且从逻辑上讲已经有几个星期了。 但是，我们需要构建后的文件副本。 这是一个大型金融机构的大型在线银行项目(因为我们在Corillian从事电子银行业务)，因此有很多人同时从事该项目。 通常，该项目是使用越来越时髦的NAnt构建的，因此这些后构建过程并不重要。 但是，有时您只想从VS.NET中进行操作。

We looked the two obvious ways:

我们看了两种明显的方式：

• Custom VS.NET Build Rules Add-In:  There's a lovely and simple sample from MSDN in VB.NET with source included.  It cleverly (and rightfully) stores it's config info in the .csproj as an extra XML section.

  自定义VS.NET构建规则加载项：VB.NET中有一个来自MSDN的可爱而简单的示例，其中包括源代码。 它巧妙地(正确地)将其配置信息存储在.csproj中作为额外的XML部分。

• Use a C++ MakeFile Project and get it to run last with Project Dependancies:  This was my first, gut reaction, backed up as at least value by Chris Sell's mention of it.  I like it since we wouldn't have to install anything assuming we already had C++ on the box. 

  使用C ++ MakeFile项目并使其在项目依赖关系中最后运行：这是我的第一个直觉，得到Chris Sell的提及，至少作为价值得到了支持。 我喜欢它，因为假设我们已经有了C ++，那么我们无需安装任何东西。

So, between a rock and a hard place, we'll use the Custom Add-In for a few months then upgrade and VS2003.  It's all good.

因此，在困难重重的环境中，我们将使用“自定义加载项”几个月，然后再升级和VS2003。 都很好。

翻译自: https://www.hanselman.com/blog/adding-pre-and-postbuild-actions-to-visual-studionet-2002