[nem-en] assembly versioning

[NoiseEHC]

What I did is
1. get svn source
2. compile via mingw
3. copy output files to c:\program files\nemerle
4. ngen them
5. try msbuild (failed)

So my idea is that c:\program files\nemerle\nemerle.dll has the same 
PublicKeyToken,
but different version number as the one in bin\debug. So the fusion 
loader messes up...

Now I have already tried the msi installer but it is strange since it is 
missing both
nemerle.dll and nemerle.compiler.dll... The reason can be that I use 
win2003 server to
develop.

BTW I did have some other version in the ngen cache but after deletion 
the problem still existed.

Kamil Skalski wrote:
> Cool! It works! But I can't reproduce your problems with incompatible versions.
> Here is what I did:
>  - I have nemerle.0.9.2 installed in my Program Files
>  - I downloaded nemerle.0.9.2 source code
>  - I changed assembly versions to 0.9.2.* in source code
>  - I tweaked your MSBuild tasks to use parameter <NoStdLib> as it was in 0.9.2
>  - I compiled all three assemblies without problems
>
> I have a little suspicion, that if I were running the recently builded
> version (with the 0.9.99.234 - like number) it could possible trigger
> the confilct.
>
> But my greater suspicion is that you had some old Nemerle.dll
> assemblies hanging around, which got loaded during compilation and
> causes conflict.
>
>
>