我正在使用安装项目来发布我的项目。我希望每个项目的版本与设置版本相同。
我想在 Visual Studio 中更改我的设置版本属性,并且在构建之后,对于要从此属性更新的所有项目版本,这可能吗?
我正在使用安装项目来发布我的项目。我希望每个项目的版本与设置版本相同。
我想在 Visual Studio 中更改我的设置版本属性,并且在构建之后,对于要从此属性更新的所有项目版本,这可能吗?
项目具有程序集和文件版本号:(不是设置版本,我相应地编辑了您的问题)
答案1:
如果您想让安装项目版本号设置程序集和文件版本号,您需要使用由构建触发的脚本/exe 来完成。
这篇关于如何自动更新程序集版本号的文章显示了一半的解决方案......
根据我所做的研究,不可能在 PreBuildEvent 中使用 SetupVersion。它没有 $SetupVersion 命令:http: //msdn.microsoft.com/en-us/library/42x5kfw4 (v=vs.80).aspx
如代码项目文章中的此评论所示,必须使用命令更改每个构建的 PreBuildEvent-set:
并不理想。
我们需要的解决方案是调用 AssemblyInfoUtil.exe 并让它从 vdproj 项目文件中读取“ProductVersion”的 PreBuildEvent。然后更新程序集版本号。
我已经修改了文章中的代码,以向您展示如何从 Setup.vdproj 读取产品版本,这就是从 PreBuildEvent 调用它的方式:
AssemblyInfoUtil.exe -setup:"C:\Program Files\MyProject1\Setup1\Setup1.vdproj" -ass:"C:\Program Files\MyProject1\AssemblyInfo.cs"
这是修改后的代码:
using System;
using System.IO;
using System.Text;
namespace AssemblyInfoUtil
{
class AssemblyInfoUtil
{
private static int incParamNum = 0;
private static string fileName = "";
private static string setupfileName = "";
private static string versionStr = null;
private static bool isVB = false;
[STAThread]
static void Main(string[] args)
{
for (int i = 0; i < args.Length; i++) {
if (args[i].StartsWith("-setup:")) {
string s = args[i].Substring("-setup:".Length);
setupfileName = int.Parse(s);
}
else if (args[i].StartsWith("-ass:")) {
fileName = args[i].Substring("-ass:".Length);
}
}
//Jeremy Thompson showing how to detect "ProductVersion" = "8:1.0.0" in vdproj
string setupproj = System.IO.File.ReadAllText(setupfileName);
int startPosOfProductVersion = setupproj.IndexOf("\"ProductVersion\" = \"") +20;
int endPosOfProductVersion = setupproj.IndexOf(Environment.NewLine, startPosOfProductVersion) - startPosOfProductVersion;
string versionStr = setupproj.Substring(startPosOfProductVersion, endPosOfProductVersion);
versionStr = versionStr.Replace("\"", string.Empty).Replace("8:",string.Empty);
if (Path.GetExtension(fileName).ToLower() == ".vb")
isVB = true;
if (fileName == "") {
System.Console.WriteLine("Usage: AssemblyInfoUtil
<path to :Setup.vdproj file> and <path to AssemblyInfo.cs or AssemblyInfo.vb file> [options]");
System.Console.WriteLine("Options: ");
System.Console.WriteLine(" -setup:Setup.vdproj file path");
System.Console.WriteLine(" -ass:Assembly file path");
return;
}
if (!File.Exists(fileName)) {
System.Console.WriteLine
("Error: Can not find file \"" + fileName + "\"");
return;
}
System.Console.Write("Processing \"" + fileName + "\"...");
StreamReader reader = new StreamReader(fileName);
StreamWriter writer = new StreamWriter(fileName + ".out");
String line;
while ((line = reader.ReadLine()) != null) {
line = ProcessLine(line);
writer.WriteLine(line);
}
reader.Close();
writer.Close();
File.Delete(fileName);
File.Move(fileName + ".out", fileName);
System.Console.WriteLine("Done!");
}
private static string ProcessLine(string line) {
if (isVB) {
line = ProcessLinePart(line, "<Assembly: AssemblyVersion(\"");
line = ProcessLinePart(line, "<Assembly: AssemblyFileVersion(\"");
}
else {
line = ProcessLinePart(line, "[assembly: AssemblyVersion(\"");
line = ProcessLinePart(line, "[assembly: AssemblyFileVersion(\"");
}
return line;
}
private static string ProcessLinePart(string line, string part) {
int spos = line.IndexOf(part);
if (spos >= 0) {
spos += part.Length;
int epos = line.IndexOf('"', spos);
string oldVersion = line.Substring(spos, epos - spos);
string newVersion = "";
bool performChange = false;
if (incParamNum > 0) {
string[] nums = oldVersion.Split('.');
if (nums.Length >= incParamNum && nums[incParamNum - 1] != "*") {
Int64 val = Int64.Parse(nums[incParamNum - 1]);
val++;
nums[incParamNum - 1] = val.ToString();
newVersion = nums[0];
for (int i = 1; i < nums.Length; i++) {
newVersion += "." + nums[i];
}
performChange = true;
}
}
else if (versionStr != null) {
newVersion = versionStr;
performChange = true;
}
if (performChange) {
StringBuilder str = new StringBuilder(line);
str.Remove(spos, epos - spos);
str.Insert(spos, newVersion);
line = str.ToString();
}
}
return line;
}
}
}
答案 2:
在我看来,更好的方法是使用Shared Assembly Info类而不是单独的 AssemblyInfo 类文件。
要实现这一点,请在名为 SharedAssemblyInfo.cs 的解决方案文件夹中创建一个文件,然后在每个项目中添加一个指向 SharedAssemblyInfo.cs 的链接。您还可以将链接的 SharedAssemblyInfo.cs 移动到 Properties 文件夹中,使其与解决方案中每个项目特定的 AssemblyInfo.cs 并排放置,如下所示。
这是一个示例 SharedAssemblyInfo.cs 文件:
using System;
using System.Reflection;
using System.Runtime.CompilerServices;
using System.Runtime.InteropServices;
// General Information about an assembly is controlled through the following
// set of attributes. Change these attribute values to modify the information
// associated with an assembly.
[assembly: AssemblyCompany("Saint Bart Technologies")]
[assembly: AssemblyProduct("Demo")]
[assembly: AssemblyCopyright("Copyright ? Saint Bart 2013")]
[assembly: AssemblyTrademark("")]
// Make it easy to distinguish Debug and Release (i.e. Retail) builds;
// for example, through the file properties window.
#if DEBUG
[assembly: AssemblyConfiguration("Debug")]
[assembly: AssemblyDescription("Flavor=Debug")] // a.k.a. "Comments"
#else
[assembly: AssemblyConfiguration("Retail")]
[assembly: AssemblyDescription("Flavor=Retail")] // a.k.a. "Comments"
#endif
[assembly: CLSCompliant(true)]
// Setting ComVisible to false makes the types in this assembly not visible
// to COM components. If you need to access a type in this assembly from
// COM, set the ComVisible attribute to true on that type.
[assembly: ComVisible(false)]
// Note that the assembly version does not get incremented for every build
// to avoid problems with assembly binding (or requiring a policy or
// <bindingRedirect> in the config file).
//
// The AssemblyFileVersionAttribute is incremented with every build in order
// to distinguish one build from another. AssemblyFileVersion is specified
// in AssemblyVersionInfo.cs so that it can be easily incremented by the
// automated build process.
[assembly: AssemblyVersion("1.0.0.0")]
// By default, the "Product version" shown in the file properties window is
// the same as the value specified for AssemblyFileVersionAttribute.
// Set AssemblyInformationalVersionAttribute to be the same as
// AssemblyVersionAttribute so that the "Product version" in the file
// properties window matches the version displayed in the GAC shell extension.
[assembly: AssemblyInformationalVersion("1.0.0.0")] // a.k.a. "Product version"
这是一个示例 AssemblyInfo.cs 文件:
// Note: Shared assembly information is specified in SharedAssemblyInfo.cs
using System.Reflection;
using System.Runtime.CompilerServices;
using System.Runtime.InteropServices;
// General Information about an assembly is controlled through the following
// set of attributes. Change these attribute values to modify the information
// associated with an assembly.
[assembly: AssemblyTitle("WindowsFormsApplication2")]
// The following GUID is for the ID of the typelib if this project is exposed to COM
[assembly: Guid("ffded14d-6c95-440b-a45d-e1f502476539")]
因此,每次您想更改所有项目的装配信息时,您都可以在一处完成。我假设您希望将 MSI 设置版本设置为与程序集版本号相同,一个手动步骤。
答案 3:
考虑改用MSBuild,它有所有这些好处,但我不确定你现在是否有时间来使用它。
答案 4:
程序集可以使用 AssemblyInfo.cs 中的以下星号语法自动增加其内部版本号:
[assembly: AssemblyVersion("1.0.0.*")]
这是一个很好的方法,因为跟踪内部版本号的目的是能够识别不同的内部版本。由于构建尚未发生,因此更改构建编号的预构建会破坏此目的。
答案 5:
此处的另一个CodeProject答案假定您要更新ProductVersion, ProductCode, PackageCode
Setup MSI Project 文件中的 。我没有那样解释你的问题,根据这个线程存在问题:
pre-build event to change setup project's ProductVersion doesn't take effect until after the build
答案 6(新):
有一些 TFS Build 插件可以设置“Assembly Info”:https ://marketplace.visualstudio.com/items?itemName=bleddynrichards.Assembly-Info-Task https://marketplace.visualstudio.com/items?itemName=bool .update-assembly-info https://marketplace.visualstudio.com/items?itemName=ggarbuglia.setassemblyversion-task
我不知道这是否能完美地解决您的问题,但您可以实现一个包含所有配置管理信息的通用类,例如:
public class VersionInfo{
public const string cProductVersion = "1.0.0"
//other version info
}
在您可以使用新类更新所有 AssemblyInfo.cs 之后:
[assembly: AssemblyVersion(VersionInfo.cProductVersion)]
我希望这有帮助。