CODEWITHSUNDEEP
asp.netc#-2.0tridionweb-deployment
Manoj Singh
Manoj Singh

Reputation: 7707

.NET Web Deployment project giving error "The located assembly's manifest definition does not match the assembly reference"

I am using .net 2.0, visual studio 2008, In my solution I have two projects (website project and references project), I build both of them seperately theya re build successfully, however when I am trying to built the solution using web deployment project it is giving below error, what can be the cause of this issue?

Error 2 Could not load file or assembly 'Tridion.Extensions.Web.UI, Version=1.0.0.19738, Culture=neutral, PublicKeyToken=7c1e07388cce59cc' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) /Careers/Controls/Application/ucBreadcrumbs.ascx 2 1 Careers_deploy

Please suggest!!

Upvotes: 0

Views: 561

Answers (3)

Dominic Cronin
Dominic Cronin

Reputation: 6201

Peter is right - fuslogvw is very useful for this kind of problem.

In addition to that, I'd suggest that an important phrase in that error message is "or one of its dependencies". I'd suggest opening up the Tridion.Extensions.Web.UI assembly with a tool that allows you to see its dependencies in the manifest. ILDASM is perfectly good for this. Equipped with the knowledge you find here, you can ensure that the other necessary assemblies are available. (It's not uncommon to find that on the system where things work, a necessary assembly is present in the GAC, while on a system where it doesn't work, it isn't.)

Upvotes: 1

Peter Kjaer
Peter Kjaer

Reputation: 4316

You may have policy files on those working systems which makes sure it loads the right version.

Anyway, your best option for troubleshooting is to run Fusion Log Viewer. Log the failures and look through the reports. Most of the time, this is enough to tell you exactly what is going wrong.

Upvotes: 1

marvc1
marvc1

Reputation: 3699

Try cleaning your solution, and see if that works.

If it doesn't try deleting the temporary ASP.NET folder which should follow a path like this:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET

Upvotes: 0

Related Questions