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 Development Question:  Multiple DNN Version CompatibleModule Development Question: Multiple DNN Version Compatible
Previous
 
Next
New Post
10/16/2008 1:55 PM
 

Hi All,

I have a question for you module developers out there:

How do you make your compiled modules work on multiple versions of DotNetNuke?  I have a component that I'm building and I'm compiling it against DotNetNuke 4.9.0, however, I know that it will work in 4.8.x because all of the functions that I'm calling are still there.  However, when I try my component in a 4.8.x site, I get this error:

error BC32206: Indirect reference is being made to assembly DotNetNuke version 
4.9.0.85, which contains 'PowerMenu.TabTree.Tab'. This Project references a
prior version of DotNetNuke version 4.8.2.0. To use 'PowerMenu.TabTree.Tab', you
must replace the reference to DotNetNuke with version 4.9.0.85 or higher.

Does anyone know how to add a reference to just "DotNetNuke" instead of "DotNetNuke 4.9.0.85"?  I tried turning off "Specific Version" in Visual Studio, but that didn't change things.

Any ideas?  Do you just always build against the oldest version of DotNetNuke that you support?

 
New Post
10/16/2008 2:48 PM
 

Hi Tony,

In your VS project tree, go to References and select the DotNetNuke.dll reference.  Then in the Properties Windows make sure Specific Version is set to False.

Thanks,

Mike

 

 
New Post
10/16/2008 2:58 PM
 

Tony,

The best practice to really ensure that you don't have issues is to build your module against the MINIMUM supported version.  For example all of my modules are built against 4.6.0.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
10/16/2008 5:34 PM
 

Tony - A quick suggestion here. 

If you're looking for a broader level of input on this module/component/menu (you appear to keep posting about it) why not consider uploading it to CodePlex like so many others in the DotNetNuke community have done with their code?  Not only would you have the benefit of generating much more feedback, but also, a deeper understanding of licensing, issue tracking, and release scheduling.  It would also avoid each individual interested user from having to email you for a !BETA! copy.

 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Development Question:  Multiple DNN Version CompatibleModule Development Question: Multiple DNN Version Compatible


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