Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
DLL Version Problems
Message
De
06/08/2004 17:19:02
 
 
À
Tous
Information générale
Forum:
ASP.NET
Catégorie:
Autre
Titre:
DLL Version Problems
Divers
Thread ID:
00931448
Message ID:
00931448
Vues:
61
I'm working through Rocky Lhotka's CSLA framework, to help me learn C# and .NET. I made a small change to one of the classes in the framework, and now I'm at my wit's end.

When running a client application, which uses the framework, I'm getting an unhandled exception:

"The located assembly's manifest definition with name 'CSLA.Server.DataPortal' does not match the assembly reference.

One of the DLL's in the framework is called CSLA, and within it is a reference to CSLA.Server.DataPortal. I have completely recompiled every class in the framework. The DLL's are not in the GAC.

Before one of the CSLA recompiles, I deleted the reference to CSLA.Server, and added it back. In the client program, I have deleted all references to the CSLA files, and added them back, and then recompiled. Every time, when compiling the client application, I get a message like the following:

The dependancy 'CSLA.Server.DataPortal, version=1.4.1678.37152 ..... in project 'ProjectTracker.Library' cannot be copied to the run directory because it would overwrite the reference 'CSLA.Server.DataPortal, version=1.4.1678.37637...'

Now, I've looked at every copy of this DLL on my system. There is not one with a version of 37152. I've looked up,down,left,and right for something refering to 37152 on my system. Oh, didn't grep for it, yet. Deleted a .user file (I think <g>) from the project, even though it didn't refer to any versions.

Recompiling the client does pull down the most current DLL into the BIN/DEBUG folder (1678.37637, in this case).

Tonight I'm going to force the DLL's to be a certain version, hoping that will help.

I've googled extensively; can't figure exactly what to do. Can anyone help me put Humpty Dumpty back together again?

< update >
The Reference Path of the project points to a location where the most current DLL's reside. Also, the DLL's are signed by a public/private key, and have been signed by the same key since the first compile.

More: In the client program, the references to the CSLA DLL's are File references, not project references. I also tried using the project tab, but browsed to the DLL files, not the framework's projects themselves.

Friday at 4 has got to be the *worst* time to ask a question. :)

Thanks for reading,
Steve Gibson
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform