[nem-en] Nemerle for VisualStudio redist.

[NoiseEHC]

That is the reason why we need "msbuild Nemerle.sln" since "msbuild 
ncc.nproj" will reference the
a newly generated Nemerle.dll. At that time you have told me that you 
really want this random
number so I am glad to see you changed your mind... :D

Kamil Skalski wrote:
>>
>> In my opinion, when Nemerle.Compiler.dll and Nemerle.Macros.dll will
>> have exactly the same version number, 0.9.3.99 or 0.9.3.61230, one 
>> can be
>> loaded from another. Nemerle.Compiler can take its own AssemblyName,
>> replace Nemerle.Compiler with Nemerle.Macros and load it from GAC.
>> For now Nemerle.Compiler does not know the version of Nemerle.Macros,
>> it only knows that it starts with 0.9.3.
>>
>
> This is a very good point :-)  So the best way would be to make sure
> that single  Nemerle/Nemerle.Compiler/Nemerle.Macros/ncc build have
> the same (generated freshly each time) number.
> Using revision number or date seems like a reasonably easy way to
> implement similar thing.
>