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...Building ExtensionsBuilding ExtensionsModulesModulesUsing DNN8 with Visual StudioUsing DNN8 with Visual Studio
Previous
 
Next
New Post
2/8/2016 11:24 AM
 

This seems like a never ending story...

Looking at this page:

http://www.dnnsoftware.com/wiki/how-to-install-the-source-package-of-dotnetnuke

You can find:

"1. It is not necessary nor recommended that you use the DotNetNuke framework source code when developing modules or other extensions. This is particularly true if you will be distributing the extensions that you create as open source contributions to the DotNetNuke community or commercially. You do not want to develop an extension against a non-standard build of DotNetNuke."

Despite what is mentioned above, as I long time DNN developer I've always found myself resorting to using the Source version of DNN. I now tried again with the Install version of DNN8 by adding it to a Visual Studio 2015 but once again I find that it immediately breaks when I try to build. So back again to the Source version of DNN8, which has it's own problems but after a while you learn how to avoid them.

So I have to ask, is anyone who is doing serious development with DNN actually using the install version or have you like us decided that you still have to use the Source version despite not having any intentions to modify the DNN source? This isn't really a major problem once you learn how to the the Source version working but then it seems strange that DNN recommends not using the Source version for development work. Or is it just us having problems with the install version and Visual Studio?

 
New Post
2/8/2016 12:32 PM
 
I'm not doing serious DDN dev at the moment. I have in the past. I have never used the Source version of DNN in my module dev environment.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
2/8/2016 12:36 PM
 
By using my templates of course.

1. Setup your development environment to run at http://dnndev.me/
2. Install the VS Templates
3. Make magic

The video tutorials for #1 and #2 are here : http://www.christoc.com/Tutorials/DNN...




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
2/8/2016 3:23 PM
 

Thanks for answering. Did/do you do most development then by having the developed module in an own project and not rebuilding the website when having made code changes but just the module? The website in the install package seem to work fine, but it just won't build in Visual Studio because of missing references etc. Like if you use Chris Hammonds exellent templates which I assume at least Chris does :)

Edit:

The problem if doing as described above as I see it is when you want to to some more "out of the box development", like using third party components like Telerik, DevExpress or similar which in turn wants to modify web.config, have to deal with CORS or similar. Then at least I want to have the web.config in my development environment, which turns into a problem if I then can't build as at least I am not able to do with the DNN8 install package.

 
New Post
2/8/2016 11:08 PM
 
Even when using Third Party components, you shouldn't need to touch the DNN source code itself.

If you need to modify the web.config, you can do so through the .DNN file of your module, on installation. It isn't all that easy, but it is possible. The only module I have that does that is my Chat modules.

https://github.com/ChrisHammond/dnnCHAT/blob/master/DnnChat.dnn#L174

<component type="Config">
<config>
<configFile>web.config</configFile>
<install>
<configuration>
<nodes>
<!-- add assembly redirect for Newtonsoft.Json v6.0.0.0-->
<node path="/configuration/runtime/ab:assemblyBinding" action="update"
targetpath="/configuration/runtime/ab:assemblyBinding[ab:dependentAssembly/ab:assemblyIdentity/@name='Newtonsoft.Json']"
collision="ignore" nameSpace="urn:schemas-microsoft-com:asm.v1" nameSpacePrefix="ab">
<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
<assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" />
<codeBase version="6.0.0.0" href="bin\dnnchat\Newtonsoft.Json.dll" />
</dependentAssembly>
</node>
</nodes>
</configuration>
</install>
<uninstall>
<configuration>
<nodes />
</configuration>
</uninstall>
</config>
</component>

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
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesUsing DNN8 with Visual StudioUsing DNN8 with Visual Studio


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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out