Assembly vs file version

[Anders Eriksson]

This might be a stupid question but ...

Why is there a need for a assembly version and a file version?

When would I use different versions for them?

// Anders

 

[Jeff Johnson]

This might be a stupid question but ...

Why is there a need for a assembly version and a file version?

When would I use different versions for them?

I certainly hope someone has a good answer for this, because I'd like to
know too.

 

[Arne Vajhøj]

This might be a stupid question but ...

Why is there a need for a assembly version and a file version?

When would I use different versions for them?

I think
http://stackoverflow.com/questions/...blyversion-assemblyfileversion-and-assemblyin
summarizes the problem pretty well.

Arne

 

[Arne Vajhøj]

http://techblog.ranjanbanerji.com/post/2008/06/26/Net-Assembly-Vs-File-Versions.aspx

I guess the way you could use the file version is to identify an
executable that runs on Vista, or Windows 7, Win 2k8 server, Windows XP,
Windows 2k3. Each on of the versions having different dependencies to
run on different platforms.

File version has to be 4 x 16 bit integers.

I guess another thing is to look a version control on file update. If
the version number for update is > than the version running on the
machine, then update application with new version. You could use
something like that if you had a custom update mechanism you wrote that
was looking at file versions to determine if application needs to be
updated with new version.

I believe that is the typical usage.

Arne