Products

Solutions

Resources

Partners

Community

Blog

About

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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Referencing Different DNN Assembly versionModule Referencing Different DNN Assembly version
Previous
 
Next
New Post
3/13/2007 3:17 PM
 
I can successfully install my module from a PA that's built both through my dnn site and put together in the file system manually, but I'm getting this beauty after adding it to a page.

Error: T6KAdmin is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\dnn4\3a00decb\13d260d8\App_Web_viewt6kadmin.ascx.fdc84d30.l0adenur.0.vb(55): error BC32206: Indirect reference is being made to assembly DotNetNuke version 4.4.1.26426, which contains 'ANPI.Modules.T6KAdmin.ViewT6KAdmin'. This Project references a prior version of DotNetNuke version 4.4.0.28454. To use 'ANPI.Modules.T6KAdmin.ViewT6KAdmin', you must replace the reference to DotNetNuke with version 4.4.1.26426 or higher. --->

A couple of points worth noting though,
- The module is not a compiled module
- The module was developed with a reference to dotnetnuke.dll version 4.4.1 and I'm attempting to intall it in a separate portal instance version 4.4.0

Everything works great as long as the portal in which the module is being intalled matches the same version as the dll that's referenced in the module.

Am I going about this the wrong way? How can I ensure that my module matches is backwards/forwards compatible at least within DNN 4.x? Any guidance would be greatly appreciated.
 
New Post
3/13/2007 6:09 PM
 

When you do a build down to a dll of any sort - you must build on the lowest version platform that your module supports.

asp.net versioning will not allow backwards referencing of versions in any way.  If your dll demands 4.1.1 and it only finds 4.4.0 then you get the error above.

While you say that your module is not a 'compiled module'  - if you are creating a .dll of any sort then - it has become a compiled module - thats what the .dll is.

Westa

 
New Post
3/13/2007 10:38 PM
 

If you use the Dynamic Module method you wont have this problem.

See: Super-Simple Module (DAL+)



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Referencing Different DNN Assembly versionModule Referencing Different DNN Assembly version


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