IO.FileLoadException After upgrade to v2.0.2

IO.FileLoadException After upgrade to v2.0.2

Old forum URL: forums.lhotka.net/forums/t/470.aspx


Jurjen posted on Monday, June 26, 2006

Hi,

I have written an application using CSLA v2.0.1, the project has a reference to the CSLA.dll wich is at a central location (for all my projects). Today I downloaded v2.0.2 and compiled it and replaced the 201 version with 202.
After loading my project I and select CSLA.dll I see that the version number is 2.0.2.0, however when I start my application I get the following exception :

An unhandled exception of type 'System.IO.FileLoadException' occurred in SecurityMaint.exe

Additional information: Could not load file or assembly 'Csla, Version=2.0.1.0, Culture=neutral, PublicKeyToken=93be5fdc093e4c30' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

It turns out that the .vbproj file in my project holds a reference (Specific Version = False) to csla.dll including the version number wich is not automatically upgraded :

    <Reference Include="Csla, Version=2.0.1.0, Culture=neutral, PublicKeyToken=93be5fdc093e4c30, processorArchitecture=MSIL">

I can solve this problem by removing the reference and recreating it but that's rather time-consuming, I've also tried refresh and clean on my project.

Am I missing something here, I've done this in VS2003 many times with no problems at all.

Jurjen.

RockfordLhotka replied on Monday, June 26, 2006

Did you try doing a Build|Clean and then a full rebuild?

Jurjen replied on Tuesday, June 27, 2006

Rocky,

I've tried that, Build - Clean Solution then Build - Rebuild Solution, but I still got the same exception.
As it turns out I was using a selfmade lookup-component wich wasn't recompiled using csla 2.0.2 so was still using 2.0.1, after rebuilding that component with 2.0.2, my project worked just fine.

Jurjen.

Copyright (c) Marimer LLC