Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Manifest Destination =/= Assembly ReferenceManifest Destination =/= Assembly Reference
Previous
 
Next
New Post
1/6/2009 3:25 PM
 
Chronofied

Joined: 10/10/2008
Posts: 26 

I was attempting to move a module from a local test site to a remote production site.
I moved the web user control and source files over to the appropriate destination folder.
The remote production site has snapped.  I now receive an error which states that:

"The located assembly's manifest definition does not match the assembly reference."

Caused somehow by an inablity to load System.Web.Extentions.
Can anybody offer some advice or pointers on why this might occur and/or what do do about it?

Thanks,

 - D

 
New Post
1/6/2009 3:28 PM
 
Chris Hammond


Chris Hammond's Avatar

Chris Hammond's Avatar

Chris Hammond's Avatar

www.christoc.com
Joined: 1/14/2003
Posts: 7319

How was the module developed? Is there a DLL in the BIN folder for the module?

Did you compile the module against a different version of the System.web.extensions?

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
1/6/2009 4:02 PM
 
Chronofied

Joined: 10/10/2008
Posts: 26

I developed the module in VB with VS2008 running a DNN build as a local site.
There are two copies of the System.Web.Extensions.DLL.
One is in the \bin and the other is in \bin\_vti_cnf.
I tried removing the module from the website directory tree on the remote site...
It did no good... I still received the same error.
Both sites were developed using System.Web.Extensions Version=3.5.0.0

Thanks,

 - D
 
New Post
1/7/2009 5:21 PM
 
Chronofied

Joined: 10/10/2008
Posts: 26

I'm replying to my own thread, because I've figured out the issue.  In case somebody has this same problem in the future, maybe they can use this information.

Though the module was developed using System.Web.Extensions Version=3.5.0.0, and the test site was running mostly 3.5 Framework, the target framework for the production site was 2.0.  When I moved the module, which requested System.Web.Extensions Version=3.5.0.0 as a dependency, the target framework for the production site was moved up to 3.5.

I cut the System.Web.Extensions Version=3.5.0.0 inherit call from the module first.  Then I switched the target back to 2.0 for the production site.  Finally, in the property pages, I removed any references to assemblies at version 3.5.  Once these tasks were accomplished, I ran (without debugging) and it fired up just fine, with the module working to boot, as soon as I'd revised the Module Definition Control.

I feel like it's something I should have spotted right away, but... oh well.  Hopefully my mistake will help someone else in the future.

 - D
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Manifest Destination =/= Assembly ReferenceManifest Destination =/= Assembly Reference


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out