Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Problems with mm 2.0.0.0 to 2.3.0.0 upgrade
Message
De
13/02/2007 15:24:34
Adam Suhayda
Jda Ehealth Systems
Illinois, États-Unis
 
 
À
Tous
Information générale
Forum:
ASP.NET
Catégorie:
The Mere Mortals .NET Framework
Titre:
Problems with mm 2.0.0.0 to 2.3.0.0 upgrade
Divers
Thread ID:
01195341
Message ID:
01195341
Vues:
68
Hi,

I've just upgraded from MM 2.0.0.0 to MM 2.3.0.0 and I'm getting a bunch of compile errors. I've updated my web.config as follows:

add assembly="Mere Mortals Framework 2005, Version=2.3.0.0, Culture=neutral, PublicKeyToken=511BD18E16C7F771"

add assembly="Mere Mortals Framework Automation 2005, Version=2.3.0.0, Culture=neutral, PublicKeyToken=94F0661EAEF8568C"

add assembly="Mere Mortals Framework Interfaces 2005, Version=2.3.0.0, Culture=neutral, PublicKeyToken=2312FEFB461DBB0E"

add assembly="Mere Mortals Framework Web Forms 2005, Version=2.3.0.0, Culture=neutral, PublicKeyToken=e35dc9ddad261220"

Additionally, I've double checked that the new assemblies exist in the WINDOWS\assembly folder.

I've also double checked my references in the VS project that I'm working on.

Unfortunately however, I'm getting a bunch of errors and warnings, and they are all complaining about being unable to load references to Version=2.0.0.0 ... however I can't seem to find any places where the old version is trying to be accessed.

Here is an example of the error I'm getting:

Error 188 Could not load file or assembly 'Mere Mortals Framework Web Forms 2005, Version=2.0.0.0, Culture=neutral, PublicKeyToken=e35dc9ddad261220' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Here is an example of the warnings I'm getting:

Warning 186 Could not resolve this reference. Could not locate the assembly "Mere Mortals Framework 2005, Version=2.0.0.0, Culture=neutral, PublicKeyToken=511bd18e16c7f771, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.


These examples are keeping the Oakleaf namespace from being accessed, and as a result any of the pages in my project that reference Oakleaf are throwing errors.

Example:

Error 101 The type or namespace name 'OakLeaf' could not be found (are you missing a using directive or an assembly reference?)


It seems to me that there is a reference or something that I'm missing (or don't know where to look for). But I can't find anything related to 2.0.0.0 in my solution..

Any thoughts?

Thanks
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform