469,574 Members | 1,643 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,574 developers. It's quick & easy.

Changing auto-build number

Is it possible to manually change the auto-build number used in VS.NET?

Thanks,
Robert
Nov 16 '05 #1
8 3088
You can set it as a constant, by editing the assembly.cs file.
The AssemblyVersion attribute:

[assembly AssemblyVersion("1.0.0.0")]

Cheers,
Branimir

--
Branimir Giurov
MCSD.NET, MCDBA
www.sofiadev.org

"Robert Misiak" <rm*****@users.cutthispartout.sourceforge.net> wrote in
message news:Ea******************@newsread1.news.pas.earth link.net...
Is it possible to manually change the auto-build number used in VS.NET?

Thanks,
Robert

Nov 16 '05 #2
Thanks, but perhaps I should have explained myself better.

I already have set AssemblyInfo.cs appropriately. However the current build
is x.x.1665.x, and soon that 3rd number will increase. Call me old
fashioned but I would like to skip the next number and go directly to
x.x.1667.x. Is that possible?

Robert

"Branimir Giurov" <br******@nospam.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
You can set it as a constant, by editing the assembly.cs file.
The AssemblyVersion attribute:

[assembly AssemblyVersion("1.0.0.0")]

Cheers,
Branimir

--
Branimir Giurov
MCSD.NET, MCDBA
www.sofiadev.org

"Robert Misiak" <rm*****@users.cutthispartout.sourceforge.net> wrote in
message news:Ea******************@newsread1.news.pas.earth link.net...
Is it possible to manually change the auto-build number used in VS.NET?

Thanks,
Robert


Nov 16 '05 #3
The easiest thing to do would be to set your version explicitly to x.x.1667.*

That should get you what you want.

--
C Addison Ritchie, MCSD
Ritch Consulting, Inc.
"Robert Misiak" wrote:
Thanks, but perhaps I should have explained myself better.

I already have set AssemblyInfo.cs appropriately. However the current build
is x.x.1665.x, and soon that 3rd number will increase. Call me old
fashioned but I would like to skip the next number and go directly to
x.x.1667.x. Is that possible?

Robert

"Branimir Giurov" <br******@nospam.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
You can set it as a constant, by editing the assembly.cs file.
The AssemblyVersion attribute:

[assembly AssemblyVersion("1.0.0.0")]

Cheers,
Branimir

--
Branimir Giurov
MCSD.NET, MCDBA
www.sofiadev.org

"Robert Misiak" <rm*****@users.cutthispartout.sourceforge.net> wrote in
message news:Ea******************@newsread1.news.pas.earth link.net...
Is it possible to manually change the auto-build number used in VS.NET?

Thanks,
Robert



Nov 16 '05 #4
Thanks, but this is an ongoing project that has been going on for over a
year - there are new builds at least once a week and frequently a few times
a day, it would be difficult to explicitly set the build number each time.

Robert
"C Addison Ritchie" <CA*************@discussions.microsoft.com> wrote in
message news:4E**********************************@microsof t.com...
The easiest thing to do would be to set your version explicitly to x.x.1667.*
That should get you what you want.

--
C Addison Ritchie, MCSD
Ritch Consulting, Inc.
"Robert Misiak" wrote:
Thanks, but perhaps I should have explained myself better.

I already have set AssemblyInfo.cs appropriately. However the current build is x.x.1665.x, and soon that 3rd number will increase. Call me old
fashioned but I would like to skip the next number and go directly to
x.x.1667.x. Is that possible?

Robert

"Branimir Giurov" <br******@nospam.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
You can set it as a constant, by editing the assembly.cs file.
The AssemblyVersion attribute:

[assembly AssemblyVersion("1.0.0.0")]

Cheers,
Branimir

--
Branimir Giurov
MCSD.NET, MCDBA
www.sofiadev.org

"Robert Misiak" <rm*****@users.cutthispartout.sourceforge.net> wrote in message news:Ea******************@newsread1.news.pas.earth link.net...
> Is it possible to manually change the auto-build number used in VS.NET? >
> Thanks,
> Robert
>
>


Nov 16 '05 #5
You can set it to whatever you want.

-Eric
Nov 16 '05 #6
Just set the value and leave it - not on each build, but on each
deployment.. I agree that the x.x.1667.* format would be best.

The only real requirement is that you change the build number when you
deploy. MSI will not recognize the revision number so each deployed version
must be unique in the major, minor, or build number.

-Eric
Nov 16 '05 #7
This doesn't seem right though because it's been x.x.1665.x for a week or
so. I also just changed the system date and recompiled and it was still
1665. The number must be stored in the project somewhere because I've found
that compiling on a different system will produce a similar build number.

Robert
"C Addison Ritchie" <CA*************@discussions.microsoft.com> wrote in
message news:91**********************************@microsof t.com...
The third number you are worried about is based on the number of days since January 1, 2000. Which means today it is going to be 1665. Tomorrow
(July 24, 2004) it will be the number which we will not mention. :-)
Sunday it will be 1668. So the answer seems to be... don't compile
tomorrow.
--
C Addison Ritchie, MCSD
Ritch Consulting, Inc.
"Robert Misiak" wrote:
Thanks, but this is an ongoing project that has been going on for over a
year - there are new builds at least once a week and frequently a few times a day, it would be difficult to explicitly set the build number each time.
Robert
"C Addison Ritchie" <CA*************@discussions.microsoft.com> wrote in
message news:4E**********************************@microsof t.com...
The easiest thing to do would be to set your version explicitly to

x.x.1667.*

That should get you what you want.

--
C Addison Ritchie, MCSD
Ritch Consulting, Inc.
"Robert Misiak" wrote:

> Thanks, but perhaps I should have explained myself better.
>
> I already have set AssemblyInfo.cs appropriately. However the current
build
> is x.x.1665.x, and soon that 3rd number will increase. Call me old
> fashioned but I would like to skip the next number and go directly
to > x.x.1667.x. Is that possible?
>
> Robert
>
>
>
> "Branimir Giurov" <br******@nospam.com> wrote in message
> news:%2****************@tk2msftngp13.phx.gbl...
> > You can set it as a constant, by editing the assembly.cs file.
> > The AssemblyVersion attribute:
> >
> > [assembly AssemblyVersion("1.0.0.0")]
> >
> > Cheers,
> > Branimir
> >
> > --
> > Branimir Giurov
> > MCSD.NET, MCDBA
> > www.sofiadev.org
> >
> >
> >
> > "Robert Misiak" <rm*****@users.cutthispartout.sourceforge.net> wrote in
> > message

news:Ea******************@newsread1.news.pas.earth link.net... > > > Is it possible to manually change the auto-build number used in

VS.NET?
> > >
> > > Thanks,
> > > Robert
> > >
> > >
> >
> >
>
>
>


Nov 16 '05 #8
Apparently I should have restarted VS.NET when changing the date; when I
changed the date to the 7-25 and restarted VS, I got build #1667. Thanks!

Robert
"C Addison Ritchie" <CA*************@discussions.microsoft.com> wrote in
message news:91**********************************@microsof t.com...
The third number you are worried about is based on the number of days since January 1, 2000. Which means today it is going to be 1665. Tomorrow
(July 24, 2004) it will be the number which we will not mention. :-)
Sunday it will be 1668. So the answer seems to be... don't compile
tomorrow.
--
C Addison Ritchie, MCSD
Ritch Consulting, Inc.
"Robert Misiak" wrote:
Thanks, but this is an ongoing project that has been going on for over a
year - there are new builds at least once a week and frequently a few times a day, it would be difficult to explicitly set the build number each time.
Robert
"C Addison Ritchie" <CA*************@discussions.microsoft.com> wrote in
message news:4E**********************************@microsof t.com...
The easiest thing to do would be to set your version explicitly to

x.x.1667.*

That should get you what you want.

--
C Addison Ritchie, MCSD
Ritch Consulting, Inc.
"Robert Misiak" wrote:

> Thanks, but perhaps I should have explained myself better.
>
> I already have set AssemblyInfo.cs appropriately. However the current
build
> is x.x.1665.x, and soon that 3rd number will increase. Call me old
> fashioned but I would like to skip the next number and go directly
to > x.x.1667.x. Is that possible?
>
> Robert
>
>
>
> "Branimir Giurov" <br******@nospam.com> wrote in message
> news:%2****************@tk2msftngp13.phx.gbl...
> > You can set it as a constant, by editing the assembly.cs file.
> > The AssemblyVersion attribute:
> >
> > [assembly AssemblyVersion("1.0.0.0")]
> >
> > Cheers,
> > Branimir
> >
> > --
> > Branimir Giurov
> > MCSD.NET, MCDBA
> > www.sofiadev.org
> >
> >
> >
> > "Robert Misiak" <rm*****@users.cutthispartout.sourceforge.net> wrote in
> > message

news:Ea******************@newsread1.news.pas.earth link.net... > > > Is it possible to manually change the auto-build number used in

VS.NET?
> > >
> > > Thanks,
> > > Robert
> > >
> > >
> >
> >
>
>
>


Nov 16 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

7 posts views Thread by David Clark | last post: by
3 posts views Thread by Geoff Soper | last post: by
2 posts views Thread by Paolo Pignatelli | last post: by
6 posts views Thread by Darian | last post: by
3 posts views Thread by naurus | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.