Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / CLR / May 2004

Tip: Looking for answers? Try searching our database.

Assembly Version Build Time

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Niall - 24 May 2004 04:46 GMT
We're using the default .Net AssemblyVersion attribute value of 1.0.*

For some reason, when we use the version number to calculate the time the
assembly was built, it's coming out an hour ahead of the actual time.

The algorithm that is used to generate the version number is supposedly:
"When specifying a version, you have to at least specify major. If you
specify major and minor, you can specify an asterisk (*) for build. This
will cause build to be equal to the number of days since January 1, 2000
local time, and for revision to be equal to the number of seconds since
midnight local time, divided by 2."
(From
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlr
fSystemReflectionAssemblyVersionAttributeClassctorTopic.asp
)

However, using this algorithm to desk check the assembly version on my own
machine, it comes up an hour ahead.

Anyone got any clues to the cause of this? It's easy enough to subtract an
hour, but I'd like to know why it's not working as intended.

Niall
Christoph Nahr - 24 May 2004 07:36 GMT
>We're using the default .Net AssemblyVersion attribute value of 1.0.*
>
>For some reason, when we use the version number to calculate the time the
>assembly was built, it's coming out an hour ahead of the actual time.

Summer time adjustment perhaps?
Signature

http://www.kynosarges.de

Niall - 25 May 2004 00:30 GMT
I tried building the assembly then checking the version straight after on
the same machine, so the clocks were the same, as were the time zones. We're
outside of daylight saving time in Australia currently

Niall

> >We're using the default .Net AssemblyVersion attribute value of 1.0.*
> >
> >For some reason, when we use the version number to calculate the time the
> >assembly was built, it's coming out an hour ahead of the actual time.
>
> Summer time adjustment perhaps?

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.