I am totally new to DNN development, I made a module using Christoc Modules, and all my logic is in the view.ascx page, I want to add a new view that basically, would be a button that when the user clicks on it the user would be redirected to the view.ascx page, I have looked everywhere to find tutorial or example that is well explained to do this step by step but I didn't find

Notes:

Check the DNN Scheduler to see if there are any active jobs that are taking longer than they should. For example, if the Site Crawler scheduler is constantly running then you should check the files in the Portals folders to make sure all of the files located in the Portals folder should actually be there. The crawler is rebuilding the index and if you have a lot of files it could take hours to complete. If the files should be there, disable the crawler scheduler and then run during your slowest time of the day (1:00 AM?). I ran into this problem on a server that had hundreds of thousands of documents in the portals folder. Ended up solving it by running the crawler between 1:00 AM and 5:00 AM for a few days until it indexed all of the files. Once the files are indexed it will only have to index changed and new files; so it should just be a burden the first time it runs.

Another possible cause are exceptions. If your site is throwing a large amount of exceptions it will slow down your site. The handling of the exceptions and then the logging of them (to the DNN EventLog table in the database and the Log4Net files) can be brutal if your site is constantly throwing exceptions. If your site is also running in DEBUG mode the performance hit is multiplied by at least 30 times due to .Net collection all of the additional information about the exception while running in debug mode. That will be brutal to your sites performance.

Check the server logs to see how often IIS is recycling the application pool for your DNN site. If it's occurring often then that is also a sign of a large amount of exceptions being thrown if you are using the default IIS application pool settings. By default, IIS will recycle your application pool if too many exceptions are thrown within a short period of time. If you also have the option set to bring up a new instance of your site and run it side by side before IIS terminates the existing instance while your site is throwing exceptions that can cause a bottleneck and will cripple performance. For this situation, I usually disable IIS from recycling the application pool if too many exceptions are thrown within a short period of time. That may not be the best option for you but if you are on top of the exceptions being thrown on the site then you can disable that and let IIS run instances side by side after an app recycle (this is nice to have when you recycle during active periods so that all existing traffic completes with the old instance and all new traffic is sent to the new instance. Once all traffic is hitting the new instance of your site IIS will terminate the older instance.)

If none of the above help, run SQL Profiler on your database to see if there is any extreme database activities going on. Also check for any db locks.

There are a lot of possible causes that can slow down DNN. The best way to find out what is going on is to run a profiler on the server (RedGate Ants profiler or Telerik (Progress) Just Trace).

Turn-key white papers are how we share some of our best advice to the public.  We take pride in ensuring that best practices are followed by all, even those that are not our current customers.

ASP.NET Ajax allows developers to add Ajax functionality to quickly introduce Ajax features without extra development, however, usage of this within DNN is met with some challenges.

Often times you might need to confirm actions with users, by creating a re-usable confirmation in the skin of your site, you can control this look and feel easily.

Working with custom solutions it is commonplace to need multiple extensions, it is possible with small modifications to package those extensions all at once.

Developers will often need to add custom functionality that ties into, or consumes data from, existing DNN tables.  There are many ways that one can do this, and this post explores one of the best ways to do this without impacting DNN.

I love sharing stories of great experiences with third-party vendors, as it doesn't happen as often as I would like.  When a recent performance issue was identified in DNN using 51 Degrees software, they jumped in and helped greatly.

Installing multiple DotNetNuke extensions at the same time can be tedious and result in unexpected downtime.  Thankfully there is an easy way to install multiple extensions at once.

In the final installation of my Enterprise Extension Development blog series we look at the actual project file structure and focus on reusability.