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

HomeHomeDevelopment and...Development and...Getting StartedGetting StartedHow to replace dotnetnuke.dll with my changed dotnetnuke.dll?How to replace dotnetnuke.dll with my changed dotnetnuke.dll?
Previous
 
Next
New Post
1/15/2014 11:22 AM
 

I have a site created on DNN 6.2.1. I needed to edit some emails behavior of standard DNN Mail.cs class. I downloaded source code of DNN 6.2.1, made necessary changes to Mail.cs class, built DNN source code solution. Then I copied changed Dotnetnuke.dll to /bin folder of my site (replaced the previous version). Everything worked fine, I saw all changes I made in Mail.cs. But after I clicked "Build Website" the new version of dotnetnuke.dll was replaced with the old one. When I open "property pages" of my web site I see ReferenceName "Dotnetnuke", Version "AutoUpdate". Where DNN takes the Dotnetnuke.dll from when building a website? Or how I can prevent replacing my modified dll with old dotnetnuke.dll?

 
New Post
1/15/2014 2:13 PM
 
first off you don't need to do a build website, all the files will background compile as it's a WSP and not a WAP. Secondly, when you do a build website it will pull the file from the release folder , I'm guessing you compiled in debug mode and not release mode.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/15/2014 2:57 PM
 
instead of referencing the assemblies in the bin folder, keep a copy of DotNetNuke.dll (and any other references) with your source code, and reference it there. Put the oldest supported version there, but develop on a newer site. Set Copy Local=False on the reference so you don't overwrite the newer version, and you should be fine.

In this way, we're able to reference DNN 4.5.3 while developing a module that runs on DNN 6.1.x. I've been using this method for years without any significant problems (except when I occasionally forget to turn off Copy Local and my DNN site mysteriously blows up).
 
New Post
1/16/2014 4:07 AM
 
Thank you for answers!
We have site /bin folder as output folder for Debug/Release mods (not /bin/debug and /bin/release). I build website in debug mode. I need to have my changed dotnetnuke.dll in website /bin folder. There is no problem if this dll will be copied to other projects while build, it's ok. I corrected the Email class exactly for emails which are sent by DNN system (not my custom projects, they even do not use this class). Everything is ok if I replace this dll in site /bin folder and do not build website BUT when I commit this changes and do a build in TeamCirty the dll will be replaced with the default one. Or e.g. I will do some changes in website code (e.g. Registration system), in this case I have to build it to see my changes.
So the questions are
1) How can I prevent dotnetnuke.dll in in my website /bin folder from replacing after build?
2) Where website is taking this dll from? Maybe it is the dll of my website? if yes - does it contain all changes I made it website code?
 
New Post
1/16/2014 7:10 AM
Accepted Answer 
Thank you for your answers!
I would like to know why dotnetnuke.dll replaces my changed dll after the build? I do not include the source code projects in my site solution. I mean that my site should take this dll from some place to include in in /bin folder. We have one folder for Debug and Release mode - /bin.

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting StartedHow to replace dotnetnuke.dll with my changed dotnetnuke.dll?How to replace dotnetnuke.dll with my changed dotnetnuke.dll?


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