All geek questions in one place

What are some good development solutions / development environments / best solutions for Dot Net Nuke modules

I have been developing modules for DNN since the second version, and then I was able to easily launch my module when I developed it in my environment, and it is still easy to deploy my module as a DLL. When version 4 came out and used a website solution (and not a web application solution). Something seems to be lost. I can continue to develop in my test environment and immediately see the changes as I make them, but the release for me was a headache.

I basically do my development for one site, in particular, I just used FTP deployment of modules on the main site after I made the changes.

I would like to create a good environment for several developers to be able to work with the module (s).

When you add material to the original control, people usually put all the DNNs in the original control so that they can make the whole solution work, or just their module, and each person needs to set up their own DNN environment dev? / P>

I would like to start organizing my module projects so that more people work for them, and I feel a little lost for some best practices both in this case and when deploying these changes on a real site.

+4
source share
2 answers

I have some detailed blog posts about this on my blog, mitchelsellers.com .

I personally use the WAP development model, and I DO NOT check the DNN solution or any core files in the source control, since I DO NOT modify the kernel for any of my clients. When working with several people, we create a similar environment for each person and can still work with each of our individual projects, from time to time we will have completely isolated development environments with separate databases and code, in other cases I worked with a common dev database data to troubleshoot problems installing the dev module.

In the WAP model, I use the method of dynamically creating my installation packages when building the project using the post-build event, and then I have a test installation that I use to verify that the packages are coming up. Debugging is then done through Attach to Process.

+3
source

I would suggest the Mitchel book if you need any kind of reference material - Wrox Professional Dotnetnuke Module Programming Module Programming - Michel Sellers

+2
source

Source: https://habr.com/ru/post/1276825/

More articles:


All Articles