Modules for DotNetNuke - Open-DNN .NET

DotNetNuke (DNN) Integration

All the components we develop, are fully integrated within DotNetNuke (and potentially any other CMS), as well as being able to be used as stand alone in any ASP.NET site.

If you want to know more, we have dedicated an entire website to Open-DNN, where you will be able to see live demos of our products. OpenDNN.com

Below, you will find a list of the components that we have developed to date, and details about their features.

Open-House - for real estate

Open-House is the new DotNetNuke based Xepient Solutions product, oriented to real estate agencies. It has a number of features that make it the best product in its category.

Multi-Language (through XML files)
DotNetNuke 3.X integration
Posibility of standalone execution
SQL Server Database. With new providers you can use other databases
Fully customizable (property features, cities, modalities, etc.)
Multiple styles (colors, font-styles, etc.) throug styleshets
Property comparison
Special Offers
4 Search types (quick, advanced, area and zip code)
Financial calculator
Intelligent search (based on the match percent of the selected features)
Asociate photos with properties with no limits
Sorting options in search results
Installation of maps for the quick search

Demo: see Open-House in action

License: see license agreement

Buy (executable): buy & download
120.00 € (EUR)

Buy (executable + source): buy & download
200.00 € (EUR)

Open-ViewState - save at server

Open-ViewSate overrides DotNetNuke's default behaviour of sending ViewState information to the client's browser. Instead, ViewState information is stored on the server, thus reducing rendering and postback times, along with increasing your .aspx page security.

How It Works

Open-ViewState is an HTTP-Module that requires no changes nor recompilation of any application source code.
You just need to add the Open-VieState .dll to the /bin directory of your application and configure it's functionality through entries in the web.config file.
When a response contains ViewState information, this is removed and placed in the server-side storage medium selected at setup (see setup information section). Instead of the entire blog of ViewState, the client's browser is served with a hidden Key, that will allow retrieval of the stored viewstate information on its next request.
On the next request, the ViewState information previously stored is retrieved to be made available for use and modification by the application as usual. Just before the resulting HTML is sent back to the client in the response, it is once again stored on the server.

Storage Options

Because it implements the Provider Pattern, you have at your disposal two ways of storing ViewState (with more to come):

Save To Cache: save ViewState in Cache, on the server
Save To XML: saves ViewState into an XML file on the server

Demo: see Open-ViewState in action

License: see license agreement

Buy: buy & download 7.00 € (EUR)

Open-KeepAlive - keep it responsive

Have you ever accessed your DotNetNuke web site after some time of inactivity, only to discovered how slow it is in servig up the first page?
Open-KeepAlive helps solving the first-hit problem.

What It Does

It keeps the site "alive", when:

The .NET process recycles its resources automatically
The web.config file is changed
A new .dll is introduced or a change of an existing .dll is made in the /bin directory

It does not keep the site "alive" when:

IIS processes are shut down, either gracefully or not

Note: Under some, but not all circumstances, when your aspnet_wp.exe or w3wp.exe is recycled or killed, the aspnet_isapi automatocally starts a new process, and Application_End is not fired. As a consequence of this behavior, sometimes the first-hit slowness will remain. The frequency of such occurrances depend on your Internet Host settings and memory capacity.

How It Does It

Open-KeepAlive is an HTTP-Module that requires no changes nor recompilation of any application source code.
You just need to add the Open-KeepAlive .dll to the /bin directory of your application and configure it's functionality through entries in the web.config file.
When the first request is made, a pool of HttpApplication instances is created and the Application_Start event is raised.
The HttpApplication instances process the first and subsequent requests.
Periodically, the HttpApplication pool instances are disposed of by the .NET runtime, and/or, the .NET runtime releases its application resources, causing the disposal of the HttpApplication pool
In either case, when the last HttpApplication instance is disposed of, the Application_End event is invoked
Just before the Application_End event is called (technically, this will happen every time an HttpApplication instance is disposed of), Open-KeepAlive will make a request to a .aspx page designated in the web.config file, thus reinitiating the HttpApplication pool
As a result, the initial delay that is the natural consequence of a page request after recycling, will not occur. Open-KeepAlive will have already made that request automatically

License: see license agreement

Buy: buy & download 3.00 € (EUR)

Open-SmartModule - .ascx into DNN

If you have already built user controls that you now want to port to DNN, or if you simply do not want to deal with the intricacies of building a DNN module, Open-SmartModule will save you all the work.

Open-SmartModule is the equivalent of a SmartPart for Microsoft SharePoint, but built to be completely user friendly and shielding the user from having to do any manual actions.

Built following the latest DNN standards, Open-SmartModule features a wizard that allows you to install your control (and all related files), set the properties of your control and even execute your Sql Scripts without ever leaving the UI interface. In less than 2 minutes you could have your regular ASP.NET user control, work as a perfectly integrated DNN module.

How It Does It

Open-SmartModule is installed like any other DNN module.
Once installed, it is available from the list of controls and you can add it to any page.
In order integrate your control into DNN, just select the edit mode of Open-SmartModule and follow the five easy steps of the installation wizard.
Step 1 will guide you through the upload of your web control's files. The interface is the familiar one used by the Upload Manager in DNN. You can upload files one by one, or in zipped format.
Step 2 will let you select the .dll(s) that your control needs. This step will automatically copy the selected .dlls to the bin folder of your DNN installation.
Step 3 will let you select the user control that you want to display on your page.
Step 4 will let you set any public properties that your control may need set, by using reflection to enumerate the properties.
Step 5 will let you execute any sql script that your control may need. The script(s) will be executed against the current DNN installation DB.

Demo: see screenshots

License: see license agreement

Buy (executable + source): buy & download 20.00 € (EUR)