By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,165 Members | 1,916 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,165 IT Pros & Developers. It's quick & easy.

Located assembly's manifest def does not match the assembly reference...

P: n/a
I'm getting an error that should be easy but I don't understand the info
structure well enough to know what's going wrong.

I've been slowly adding classes and projects to a solution for a while.
There's a single test exe and a number of of# library classes. I needed to
move two of the projects down one directory from their original position and
did so my making the appropriate directory, copying the source to that
directory, deleting the original from the solution, adding the moved copy to
the solution and then modified the various project properties so that the
post copy command put the assemblies in the proper place, the relative path
to the key files was adjusted and the project references were changed to use
the new projects instead of the old one. The project build successfully.
However, when the test app runs and tries to create an Account class, an
exception is thrown because "The located assembly's manifest definition with
name 'BCGI.Business.Security.Common' does not match the assembly reference.'

The test code calls into a function that resides in Account, one of the
projects that was moved, and Account references the
BCGI.Business.Security.Common assembly. I've gone through the various
projects, deleted and then re-added the references but the problem doesn't
go away.

1) How do I fix the problem?
2) What does moving two projects have to do with changing the requested
version numbers?
3) How does the system know what version numbers it is looking for?

--
Richard Lewis Haggard
www.Haggard-And-Associates.com
Feb 13 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Richard Lewis Haggard wrote:
I'm getting an error that should be easy but I don't understand the
info structure well enough to know what's going wrong.

I've been slowly adding classes and projects to a solution for a
while. There's a single test exe and a number of of# library
classes. I needed to move two of the projects down one directory from
their original position and did so my making the appropriate
directory, copying the source to that directory, deleting the
original from the solution, adding the moved copy to the solution and
then modified the various project properties so that the post copy
command put the assemblies in the proper place, the relative path to
the key files was adjusted and the project references were changed to
use the new projects instead of the old one. The project build
successfully. However, when the test app runs and tries to create an
Account class, an exception is thrown because "The located assembly's
manifest definition with name 'BCGI.Business.Security.Common' does
not match the assembly reference.'

The test code calls into a function that resides in Account, one of
the projects that was moved, and Account references the
BCGI.Business.Security.Common assembly. I've gone through the various
projects, deleted and then re-added the references but the problem
doesn't go away.

1) How do I fix the problem?
2) What does moving two projects have to do with changing the
requested version numbers?
3) How does the system know what version numbers it is looking for?


is BCGI.Business.Security.Common a signed assembly? If so, please
check the version number by right-clicking the dll, -> properties ->
version tab and compare that with the version number shown in the
references in the project in vs.net.

FB

--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
Feb 14 '06 #2

P: n/a
Yes, it is a signed assembly. The versions are the same. The version number
from the DLL's properties is the same as the version that is displayed in
the reference section of the failing assembly.
--
Richard Lewis Haggard
www.Haggard-And-Associates.com
"Frans Bouma [C# MVP]" <pe******************@xs4all.nl> wrote in message
news:xn***************@news.microsoft.com...
Richard Lewis Haggard wrote:
I'm getting an error that should be easy but I don't understand the
info structure well enough to know what's going wrong.

I've been slowly adding classes and projects to a solution for a
while. There's a single test exe and a number of of# library
classes. I needed to move two of the projects down one directory from
their original position and did so my making the appropriate
directory, copying the source to that directory, deleting the
original from the solution, adding the moved copy to the solution and
then modified the various project properties so that the post copy
command put the assemblies in the proper place, the relative path to
the key files was adjusted and the project references were changed to
use the new projects instead of the old one. The project build
successfully. However, when the test app runs and tries to create an
Account class, an exception is thrown because "The located assembly's
manifest definition with name 'BCGI.Business.Security.Common' does
not match the assembly reference.'

The test code calls into a function that resides in Account, one of
the projects that was moved, and Account references the
BCGI.Business.Security.Common assembly. I've gone through the various
projects, deleted and then re-added the references but the problem
doesn't go away.

1) How do I fix the problem?
2) What does moving two projects have to do with changing the
requested version numbers?
3) How does the system know what version numbers it is looking for?


is BCGI.Business.Security.Common a signed assembly? If so, please
check the version number by right-clicking the dll, -> properties ->
version tab and compare that with the version number shown in the
references in the project in vs.net.

FB

--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

Feb 14 '06 #3

P: n/a
I finally just blew everything thing away and manually rebuilt the entire
solution from ground zero. That works. Thanks for the help anyway.
--
Richard Lewis Haggard
www.Haggard-And-Associates.com
"Richard Lewis Haggard" <HaggardAtWorldDotStdDotCom> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Yes, it is a signed assembly. The versions are the same. The version
number from the DLL's properties is the same as the version that is
displayed in the reference section of the failing assembly.
--
Richard Lewis Haggard
www.Haggard-And-Associates.com
"Frans Bouma [C# MVP]" <pe******************@xs4all.nl> wrote in message
news:xn***************@news.microsoft.com...
Richard Lewis Haggard wrote:
I'm getting an error that should be easy but I don't understand the
info structure well enough to know what's going wrong.

I've been slowly adding classes and projects to a solution for a
while. There's a single test exe and a number of of# library
classes. I needed to move two of the projects down one directory from
their original position and did so my making the appropriate
directory, copying the source to that directory, deleting the
original from the solution, adding the moved copy to the solution and
then modified the various project properties so that the post copy
command put the assemblies in the proper place, the relative path to
the key files was adjusted and the project references were changed to
use the new projects instead of the old one. The project build
successfully. However, when the test app runs and tries to create an
Account class, an exception is thrown because "The located assembly's
manifest definition with name 'BCGI.Business.Security.Common' does
not match the assembly reference.'

The test code calls into a function that resides in Account, one of
the projects that was moved, and Account references the
BCGI.Business.Security.Common assembly. I've gone through the various
projects, deleted and then re-added the references but the problem
doesn't go away.

1) How do I fix the problem?
2) What does moving two projects have to do with changing the
requested version numbers?
3) How does the system know what version numbers it is looking for?


is BCGI.Business.Security.Common a signed assembly? If so, please
check the version number by right-clicking the dll, -> properties ->
version tab and compare that with the version number shown in the
references in the project in vs.net.

FB

--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------


Feb 16 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.