Hello LLBLGeners,

I am in the process of upgrading an ASP.NET web application to LLBLGen 3.5 from version 3.1. I have regenerated the LLBLGen source from the 3.5 designer and built the 2 generated projects. I have verified that the version of the SD.LLBLGen.* DLLs in the bin directories are of version 3.5. In my web application I have removed all project references to version 3.1 DLLs and added references to version 3.5. The application builds fine but when I attempt to view the app from a browser i receive this exception:

Could not load file or assembly 'SD.LLBLGen.Pro.DQE.SqlServer.NET20, Version=3.1.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

I searched through all of the application source code files for the phrase "3.1" in case I missed a project reference and I find nothing.

I have deleted Temporary ASP.NET Files and recycled IIS but I still get that exception.

Any ideas?

Most probably the DBSpecific project is referencing the 3.1 version of the DQE. Please remove this reference and let it reference v.3.5, then build all your projects.

this is what I see in the DBSpecific project file. It looks correct. I also checked the other project file and that is below. It also looks correct.

<Reference Include="SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=3.5.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27, processorArchitecture=MSIL">
<SpecificVersion>True</SpecificVersion>
<HintPath>C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.5\Frameworks\LLBLGen Pro\RuntimeLibraries\Net2.0\</HintPath>
</Reference>
<Reference Include="SD.LLBLGen.Pro.DQE.SqlServer.NET20, Version=3.5.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27, processorArchitecture=MSIL">
<SpecificVersion>True</SpecificVersion>
<HintPath>C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.5\Frameworks\LLBLGen Pro\RuntimeLibraries\Net2.0\</HintPath>
</Reference>

<Reference Include="SD.LLBLGen.Pro.LinqSupportClasses.NET35, Version=3.5.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27, processorArchitecture=MSIL">
<SpecificVersion>True</SpecificVersion>
<HintPath>C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.5\Frameworks\LLBLGen Pro\RuntimeLibraries\Net3.5\</HintPath>
</Reference>
<Reference Include="SD.LLBLGen.Pro.QuerySpec, Version=3.5.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27, processorArchitecture=MSIL">
<SpecificVersion>True</SpecificVersion>
<HintPath>C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.5\Frameworks\LLBLGen Pro\RuntimeLibraries\Net3.5\</HintPath>
</Reference>
<Reference Include="SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=3.5.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27, processorArchitecture=MSIL">
<SpecificVersion>True</SpecificVersion>
<HintPath>C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.5\Frameworks\LLBLGen Pro\RuntimeLibraries\Net2.0\</HintPath>
</Reference>

Mmm That reference should be somewhere, maybe in another project that is part of your solution or in a /obj temp file.

If nothing helps maybe you could attach your zipped solution, without /bin folders nor .dlls, just the source to see if we can found something. You can do that in a HelpDesk thread which is private.

I figured it out. I wasn't directly referencing the older version of SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll but I was referencing an older version of the 2 generated DLLs (e.g. DBSpecific) and those had a dependency on the older version of the SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll.

Thanks for your suggestions

Aha!

Thanks for the feedback. Good you sorted it out