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.0Why am I receiving this reference error for a converted 3.x module to 4.x?Why am I receiving this reference error for a converted 3.x module to 4.x?
Previous
 
Next
New Post
2/22/2007 7:26 PM
 

I am trying to get used to the new 'Add Item' method of DNN 4 w/VS 2005.  In converting a module from DNN 3 to DNN 4, I am getting the following error:

Error 4 'Public WriteOnly Property CreatedByUser() As String' is declared in project 'DotNetNuke.dll', which is not referenced by project '3_DesktopModules_Word_EditWord.ascx'. Add a reference to 'DotNetNuke.dll' to your project '3_DesktopModules_Word_EditWord.ascx'. This error could also be due to mixing a file reference with a project reference to assembly 'DotNetNuke.  In this case, try replacing the file reference to 'DotNetNuke.dll' in project 'DotNetNuke.News' with a project reference to 'DotNetNuke.Library'. C:\websites\mysite\website\DesktopModules\Word\EditWord.ascx.vb 73 15 http://192.168.0.89/

There is not a 'references' folder any longer in the module, so I have no clue exactly where I should be adding a reference to the DotNetNuke.dll.  There is already a reference to the dll in the only references file I can see, which is the DNN solution.

Could someone point me to what this error means?  And where to add this reference?

One a related note, is anyone considering adding a VS Template for a DNN Module project?  Like it used to be?  I would try it, but I know nothing about creating VS templates, and until I understand it, it wouldn't do anyone any good anyway.

Thanks for your help.  Just to be clear, I am using the DNN solution with the source download, created the DNN module with 'Add New Item', select DotNetNuke module, and the name of the Module is 'Word'.  I then updated all the Edit, Info, View, etc. files with the code from my 3.x module, making the changes in the ascx files as specified elsewhere.

 

 
New Post
2/23/2007 10:32 PM
 

Just so others who may search these forums will know, I received this error because I had loaded (and had to convert to 4.x) the News Feed project into my DotNetNuke web site.  Because of this, there was an issue with referencing the same dotnetnuke.dll.  As soon as I unloaded the News project, everything worked fine.

Is there any discussion of making the DNN projects so they are 4.x compatible?  It appears that some of the projects (Wiki, News, Announcements at least) are still in 3.x project format.

Anyway, for anyon who is building modules, my advice is to not load any of the DNN projects into the solution.  Unexpected results can follow.

 
New Post
2/24/2007 5:35 PM
 
when using wap to develop modules, the references are shown if you click Show All. Alternatively double click My Project or right click The Project name and select Properties. it's under the references tab.

Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
New Post
2/24/2007 10:22 PM
 
Thanks Hooligannes.  I did find the references for the solution, but I never did find the references for the DNN module.  I think it's because it's not a project in WAP, but an 'item'.  For instance, I never created the project that is referenced ('3_DesktopModules_Word'), nor is that project listed in my solution.  I'm still getting used to the 'dynamic compilation' stuff.  I appreciate your response.  I mean, I solved the problem, I just don't understand why unloading the News Feed project fixed the issue.  Sooner or later a light bulb will go off...I hope.
 
New Post
2/25/2007 10:07 PM
 

In .net 2, AFAIR, compiling against newer versions of DNN, will make the module not work with a previous one. I think iIt's an issue with strongly named assemblies. SO you need to compile against the same dotnetnuke version you'll use in deployment.

Check this article to move from DNN3 to DNN4 as a WAP module


Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Why am I receiving this reference error for a converted 3.x module to 4.x?Why am I receiving this reference error for a converted 3.x module to 4.x?


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