product version no

[John]

Hi

How can I change the product version number that is returned by
Application.Pro ductVersion?

Thanks

Regards

[Ken Tucker [MVP]]

Hi,

You can change it in the AssemblyInfo.vb file.

Ken
--------------
"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:uj******** *****@tk2msftng p13.phx.gbl...

Hi

How can I change the product version number that is returned by
Application.Pro ductVersion?

Thanks

Regards

[Jay B. Harlow [MVP - Outlook]]

John,
As Ken stated, you change it in the AssemblyInfo.vb file. Actually you
change it with AssemblyInforma tionVersion attribute, which I normally place
in the AssemblyInfo.vb file along with all the other attributes dealing with
the assembly.

Normally you will only find the AssemblyVersion attribute in the
AssemblyInfo.vb file. You can add the AssemblyInforma tionVersion and
AssemblyFileVer sion attributes if you want. All three values will use
AssemblyVersion if you do not include the other two attributes.

AssemblyVersion - the version number of the assembly.
AssemblyInforma tionVersion - the version number of the product itself
AssemblyFileVer sion - the version number of the file

In my current project I am using both the AssemblyVersion number & the
AssemblyInforma tionVersion.

Hope this helps
Jay

"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:uj******** *****@tk2msftng p13.phx.gbl...

Hi

How can I change the product version number that is returned by
Application.Pro ductVersion?

Thanks

Regards

[John]

There is an * in the version number. Where is the value for * coming from?
Also, is there an automatic way to increase the no with every build?

Thanks

Regards
"Jay B. Harlow [MVP - Outlook]" <Ja********@ema il.msn.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

John,
As Ken stated, you change it in the AssemblyInfo.vb file. Actually you
change it with AssemblyInforma tionVersion attribute, which I normally place in the AssemblyInfo.vb file along with all the other attributes dealing with the assembly.

Normally you will only find the AssemblyVersion attribute in the
AssemblyInfo.vb file. You can add the AssemblyInforma tionVersion and
AssemblyFileVer sion attributes if you want. All three values will use
AssemblyVersion if you do not include the other two attributes.

AssemblyVersion - the version number of the assembly.
AssemblyInforma tionVersion - the version number of the product itself
AssemblyFileVer sion - the version number of the file

In my current project I am using both the AssemblyVersion number & the
AssemblyInforma tionVersion.

Hope this helps
Jay

"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:uj******** *****@tk2msftng p13.phx.gbl...

Hi

How can I change the product version number that is returned by
Application.Pro ductVersion?

Thanks

Regards

[Jay B. Harlow [MVP - Outlook]]

John,

Also, is there an automatic way to increase the no with every build? The * in the version number, is the automatic way of changing the number
with every build, note it does not actually increment the number.

The * actually causes the current date & time to be encoded into the build
number, I'm not sure if its actual date & time or when you last started
VS.NET.

I believe the only way to get different behavior is to modify the file
during the build event with a VS.NET add-in or macro.

Hope this helps
Jay

"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:OB******** ******@TK2MSFTN GP12.phx.gbl... There is an * in the version number. Where is the value for * coming from?
Also, is there an automatic way to increase the no with every build?

Thanks

Regards
"Jay B. Harlow [MVP - Outlook]" <Ja********@ema il.msn.com> wrote in message news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

John,
As Ken stated, you change it in the AssemblyInfo.vb file. Actually you
change it with AssemblyInforma tionVersion attribute, which I normally

place

in the AssemblyInfo.vb file along with all the other attributes dealing

with

the assembly.

Normally you will only find the AssemblyVersion attribute in the
AssemblyInfo.vb file. You can add the AssemblyInforma tionVersion and
AssemblyFileVer sion attributes if you want. All three values will use
AssemblyVersion if you do not include the other two attributes.

AssemblyVersion - the version number of the assembly.
AssemblyInforma tionVersion - the version number of the product itself
AssemblyFileVer sion - the version number of the file

In my current project I am using both the AssemblyVersion number & the
AssemblyInforma tionVersion.

Hope this helps
Jay

"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:uj******** *****@tk2msftng p13.phx.gbl...

Hi

How can I change the product version number that is returned by
Application.Pro ductVersion?

Thanks

Regards

[Herfried K. Wagner [MVP]]

* "John" <jo**@nospam.in fovis.co.uk> scripsit:

How can I change the product version number that is returned by
Application.Pro ductVersion?

Basic information on versioning:

<http://msdn.microsoft. com/library/en-us/dndotnet/html/managevers.asp>
<http://msdn.microsoft. com/library/en-us/dnbda/html/tdlg_ch5.asp>
<http://msdn.microsoft. com/library/en-us/cptutorials/html/versioning_comp onents.asp>

Parts of the version number:

Main version
"Product" version.
Sub version
Sub version, for example Service Pack.
Build
During development, auto-increment.
Revision
Hotfix or Quick Fix Engineering (QFE).

When using auto incrementation of numbers, the build number contains the
number of days since January, 2000; the revision contains the number of
seconds since midnight divided by 2.

The version number can be changed in the file "AssemblyInfo.v b". The
version number will updated automatically when re-opening the solution.

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
<http://www.mvps.org/dotnet>

[John]

I have got AssemblyVersion ("1.0.*") in my assembly.vb. No matter how many times I reopen, change or rebuild the project, my build remains the same. For some reason automatic build increment is not working for me. Any ideas?
"Jay B. Harlow [MVP - Outlook]" <Ja********@ema il.msn.com> wrote in message news:e%******** *******@TK2MSFT NGP10.phx.gbl.. .

John,

Also, is there an automatic way to increase the no with every build?

The * in the version number, is the automatic way of changing the number
with every build, note it does not actually increment the number.

The * actually causes the current date & time to be encoded into the build
number, I'm not sure if its actual date & time or when you last started
VS.NET.

I believe the only way to get different behavior is to modify the file
during the build event with a VS.NET add-in or macro.

Hope this helps
Jay

"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:OB******** ******@TK2MSFTN GP12.phx.gbl...

There is an * in the version number. Where is the value for * coming from?
Also, is there an automatic way to increase the no with every build?

Thanks

Regards
"Jay B. Harlow [MVP - Outlook]" <Ja********@ema il.msn.com> wrote in

message

news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

John,
As Ken stated, you change it in the AssemblyInfo.vb file. Actually you
change it with AssemblyInforma tionVersion attribute, which I normally

place

in the AssemblyInfo.vb file along with all the other attributes dealing

with

the assembly.

Normally you will only find the AssemblyVersion attribute in the
AssemblyInfo.vb file. You can add the AssemblyInforma tionVersion and
AssemblyFileVer sion attributes if you want. All three values will use
AssemblyVersion if you do not include the other two attributes.

AssemblyVersion - the version number of the assembly.
AssemblyInforma tionVersion - the version number of the product itself
AssemblyFileVer sion - the version number of the file

In my current project I am using both the AssemblyVersion number & the
AssemblyInforma tionVersion.

Hope this helps
Jay

"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:uj******** *****@tk2msftng p13.phx.gbl...
> Hi
>
> How can I change the product version number that is returned by
> Application.Pro ductVersion?
>
> Thanks
>
> Regards
>
>

[Jay B. Harlow [MVP - Outlook]]

John,
Not sure what to offer, as it works for me.

Which version of VS.NET are you using? VS.NET 2002, VS.NET 2003, a pre 2002
beta, or the Whidbey beta/preview?

Hope this helps
Jay

"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:%2******** *******@TK2MSFT NGP12.phx.gbl.. .
I have got AssemblyVersion ("1.0.*") in my assembly.vb. No matter how many
times I reopen, change or rebuild the project, my build remains the same.
For some reason automatic build increment is not working for me. Any ideas?
"Jay B. Harlow [MVP - Outlook]" <Ja********@ema il.msn.com> wrote in message
news:e%******** *******@TK2MSFT NGP10.phx.gbl.. .

John,

Also, is there an automatic way to increase the no with every build?

The * in the version number, is the automatic way of changing the number
with every build, note it does not actually increment the number.

The * actually causes the current date & time to be encoded into the build
number, I'm not sure if its actual date & time or when you last started
VS.NET.

I believe the only way to get different behavior is to modify the file
during the build event with a VS.NET add-in or macro.

Hope this helps
Jay

"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:OB******** ******@TK2MSFTN GP12.phx.gbl...

There is an * in the version number. Where is the value for * coming from? Also, is there an automatic way to increase the no with every build?

Thanks

Regards
"Jay B. Harlow [MVP - Outlook]" <Ja********@ema il.msn.com> wrote in

message

news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

John,
As Ken stated, you change it in the AssemblyInfo.vb file. Actually you
change it with AssemblyInforma tionVersion attribute, which I normally

place

in the AssemblyInfo.vb file along with all the other attributes

dealing with

the assembly.

Normally you will only find the AssemblyVersion attribute in the
AssemblyInfo.vb file. You can add the AssemblyInforma tionVersion and
AssemblyFileVer sion attributes if you want. All three values will use
AssemblyVersion if you do not include the other two attributes.

AssemblyVersion - the version number of the assembly.
AssemblyInforma tionVersion - the version number of the product itself
AssemblyFileVer sion - the version number of the file

In my current project I am using both the AssemblyVersion number & the
AssemblyInforma tionVersion.

Hope this helps
Jay

"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:uj******** *****@tk2msftng p13.phx.gbl...
> Hi
>
> How can I change the product version number that is returned by
> Application.Pro ductVersion?
>
> Thanks
>
> Regards
>
>

[John]

vs.net 2003 upgrade

"Jay B. Harlow [MVP - Outlook]" <Ja********@ema il.msn.com> wrote in message
news:e$******** ******@TK2MSFTN GP10.phx.gbl...

John,
Not sure what to offer, as it works for me.

Which version of VS.NET are you using? VS.NET 2002, VS.NET 2003, a pre 2002 beta, or the Whidbey beta/preview?

Hope this helps
Jay

"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:%2******** *******@TK2MSFT NGP12.phx.gbl.. .
I have got AssemblyVersion ("1.0.*") in my assembly.vb. No matter how many
times I reopen, change or rebuild the project, my build remains the same.
For some reason automatic build increment is not working for me. Any ideas?

"Jay B. Harlow [MVP - Outlook]" <Ja********@ema il.msn.com> wrote in message news:e%******** *******@TK2MSFT NGP10.phx.gbl.. .

John,

Also, is there an automatic way to increase the no with every build?

The * in the version number, is the automatic way of changing the number
with every build, note it does not actually increment the number.

The * actually causes the current date & time to be encoded into the build

number, I'm not sure if its actual date & time or when you last started
VS.NET.

I believe the only way to get different behavior is to modify the file
during the build event with a VS.NET add-in or macro.

Hope this helps
Jay

"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:OB******** ******@TK2MSFTN GP12.phx.gbl...

There is an * in the version number. Where is the value for * coming

from? Also, is there an automatic way to increase the no with every build?

Thanks

Regards
"Jay B. Harlow [MVP - Outlook]" <Ja********@ema il.msn.com> wrote in

message

news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
> John,
> As Ken stated, you change it in the AssemblyInfo.vb file. Actually you > change it with AssemblyInforma tionVersion attribute, which I normally place
> in the AssemblyInfo.vb file along with all the other attributes dealing with
> the assembly.
>
> Normally you will only find the AssemblyVersion attribute in the
> AssemblyInfo.vb file. You can add the AssemblyInforma tionVersion and
> AssemblyFileVer sion attributes if you want. All three values will use > AssemblyVersion if you do not include the other two attributes.
>
> AssemblyVersion - the version number of the assembly.
> AssemblyInforma tionVersion - the version number of the product itself > AssemblyFileVer sion - the version number of the file
>
> In my current project I am using both the AssemblyVersion number & the > AssemblyInforma tionVersion.
>
> Hope this helps
> Jay
>
> "John" <jo**@nospam.in fovis.co.uk> wrote in message
> news:uj******** *****@tk2msftng p13.phx.gbl...
> > Hi
> >
> > How can I change the product version number that is returned by
> > Application.Pro ductVersion?
> >
> > Thanks
> >
> > Regards
> >
> >
>
>