It's occasionally tricky/troublesome to pass the current Portald from your DotNetNuke control that inherits PortalModuleBase so that it can be used in your business object logic. A trick that I learned looking at another developer's code recently is to get the current PortalId from PortalController.GetCurrentPortalSettings().PortalId. CurrentPortalSettings is set for every request, so it is always the value that you are looking for.

Hope it helps,

I tend to run one of the latest versions of DotNetNuke for my development website, however I still want to compile against an older version so that my assemblies are compatible with the older versions.  So, I create a folder outside of my website (C:\Assemblies) with a directory for each version of DNN (and the Ajax Control Toolkit) that I might want to target.  I fill each directory with the contents of the bin folder from the DNN install (or Ajax Control Toolkit website), and then set a resource path in my project that points to that specific directory.  Voila, running 4.7.0, compiling against 4.5.1.

You'll need to make sure that your project doesn't set the Copy Local property on each reference, since that'll copy the old assembly over the new assembly and break your website.

Hope it helps,

We  have finally made the first public release of Engage: Locator on Engage Modules.  If you want to make it easy for the visitors to your website find your business locations, Engage: Locator is the solution. We've invested a lot of time in making it user friendly and configurable and has finally reached a point where we could release it.  Have a look on our demo site and see if this could add a nice touch to your site.

If you have recently edited your reporting services web.config and can no longer access your reports you may want to check if your web.config file contains an xmlns attribute on the configuration element. If it does, you will not be able to access your report manager.  Simply removing the attribute will solve this issue.

I ran into this issue today after i edited a property in the web.config using the IIS tool (under asp.net tab). As i had no idea what had originally caused the issue it took a few hours to figure out that it was because i had edited the web.config with IIS.

Here is the error message that the report manager would display:

"The report server is not responding. Verify that the report server is running and can be accessed from this computer."

Here is the error message from the log file:& ...

Best practices for developing DotNetNuke modules dictates that we use the development.config as our web.config, which includes running our development sites under Medium Trust.  This is necessary so that we don't inadvertently introduce code that requires Full Trust into our module and thereby restrict it to customers running in Medium Trust.

However, while in Medium Trust, certain data visualizers in Visual Studio don't work (namely, the DataTable and DataSet visualizers).  You'll see a message like "The application you are debugging has insufficient privileges to allow the use of custom visualizers. Please see the documentation for the list of required privileges."  I've been occasionally frustrated for a number of months because I couldn't figure out why Visual Studio was barking at me when all I wanted to do was use their built-in visualizer.  Finally, I found t ...

We have just released a minor update to Engage: Rotator, our content rotating module for DotNetNuke.  This fixes issues some folks were seeing where content would "jump" a bit when it was rotating.  If you don't already have it, pick up a copy from our Buy Now page on Engage Modules.