|
| why won't the build number auto increment? |
|
|
|
|
| Messages |
|
Related Types |
This message was discovered on microsoft.public.dotnet.framework.compactframework.
| Jesse |
My project's AssemblyInfo.vb file says:
<Assembly: AssemblyVersion("1.0.*")>
But when I rebuild, I keep getting the same old build number.
Any idea why?
|
|
|
| |
|
| |
| |
| Tim Wilson |
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/tdlg_ch5.asp
"Note For a Microsoft Visual Basic® .NET project with an AssemblyVersion
set to "1.0.*", the assembly version is only updated the first time the
project is rebuilt within the Visual Studio .NET integrated development
environment (IDE). The version number remains constant for subsequent
rebuilds within the same instance of Visual Studio .NET. This does not
represent a problem because the assembly version is for information only in
assemblies that do not have a strong name. For strong named assemblies, you
should avoid the use of wild characters in the AssemblyVersion attribute, as
explained in the following section.
For C# projects with an AssemblyVersion set to "1.0.*", the assembly version
is updated every time the project is rebuilt."
--
Tim Wilson
..Net Compact Framework MVP
{cf147fdf-893d-4a88-b258-22f68a3dbc6a}
"Jesse" <Click here to reveal e-mail address> wrote in message
news:Click here to reveal e-mail address...
[Original message clipped]
|
|
|
| |
|
| |
|
|
|
|
|
|
|
|
BootFX
Reliable and powerful .NET application framework. |
|
|
|
|
|
|
