[Mono-dev] Problem with reference not refreshed or specific version binding
Robert Jordan
robertj at gmx.net
Fri May 22 11:34:02 EDT 2009
APS wrote:
> Anyone have a clue?
Remove the wildcards from your AssemblyVersion attributes:
[assembly: AssemblyVersion("1.0.0.0")]
and only increment the version if the API really changed.
Robert
>
> At 09.36 20/05/2009, APS wrote:
>> Hi,
>> I have a similar problem on a console application that use a couple
>> of libraries. The main executable is built against 1.1 version of
>> libraries but I installed it the first time (so without replacing
>> file already run) with version 1.2 of the same libraries.
>> With MS Framework it works well, in mono I receive an error saying
>> that it doesn't found version 1.1.
>> In Mono specific version reference is implicit? I always have to
>> rebuild to be able to use a new version of a library? Or there's some
>> configuration? Or I'm doing something wrong (the most probably option ehehe)?
>>
>>
>> At 19.53 14/05/2009, Gonzalo Paniagua Javier wrote:
>>> On Thu, 2009-05-14 at 18:34 +0200, APS wrote:
>>>> Hi,
>>>>
>>>> I'm working on a webapplication with mod_mono. The web app runs well
>>>> but if I try to update an assembly with a different version I obtain a
>>>> Compilation Error
>>>> saying that an assembly could not be loaded.
>>>> In detailed errors I see that the problem is that a referenced
>>>> assembly (the dll I updated) version 1.2.3 cannot be found.
>>>> My new assembly is inside bin but it's has a new version (1.2.4)
>>>> I checked the reference in the main assembly and "specific version" is
>>>> false, so it should work with every assembly version. I first removed
>>>> the 1.2.3 version and then placed the new version as described into
>>>> faqs.
>>>> I checked the assembly that is specified on the gmcs command line, as
>>>> specified in detailed error (
>>>>
>> tmp/wwwrun-temp-aspnet-0/37c30bc1/assembly/shadow/409bd53a/54dc730a_1447a630_00000001/)
>>
>>> and there is the right file, the 1.2.4 version.
>>>> What I'm doing wrong? why it seems to keep on searching for the old
>>>> specific version? Thanks in advance.
>>> Mono does not deal well with 2 assemblies that are different only in the
>>> version number. I believe this is already in bugzilla (and it will be
>>> for a while)
>>>
>>> -Gonzalo
>>>
>>>
>>> _______________________________________________
>>> Mono-devel-list mailing list
>>> Mono-devel-list at lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
More information about the Mono-devel-list
mailing list