Hello Adrian,
>
no this does not work for vb 2008. Any thoughts?
Works for me.
What version *is* being generated ?
Can you set the version to a hard coded value (say "2.5.3.9") rather than
an auto increment?
Does this affect the resultant dll?
Are you sure you're checking the dll that's being built.
Perhaps a configuration change has changed the build directory and you are
looking at an old version? (Check the modified date)
Is your Assemblyinfo.vb set to something other than "compile"?
Just a few thoughts... Jeff's solution should be correct
--
Rory