Is the following a true statement?  Any web application that was created using ASP.NET can be made into a DNN Module. 

In other words, are there any intracacies within the DNN framework that would cause something to be impossible or real hard to do as a dnn module?

I'm definitely not looking for criticism of DNN, I love DNN, I just think it would be a very interesting topic to see what can and can't be done as a dnn module.

It can't slice,dice, or make julienne fries!!!

As far as I've seen or heard there's nothing that can't be made into a DNN module. It may get a bit tricky/confusing when it comes to mulitple pages but it can be done.

Another hard conversion would be for an application that uses an httpmodule to intercept the request. The one that comes to mind is .Text. .Text is dependent on the URL path that gets sent to the application. This path is virtual and parsed within the module. Since DNN uses it's own httpmodule to deal with tab names the same way .Text does, it would get pretty confusing to sort it between the applications.

To have DNN fully integrated into Active directory at this point is more than just a module change.  There are good AD modules but its not complete AD, at least that was the latest I heard.  There is a AD subproject I hear.

Another thing,  so far there is no clear documentation that lists what the limitations are for DNN, from a resource perspective.
no charts, statistics. People ask for that.

as you can tell...integration issues...esp those that have been designed to be in their own application domain and rely on that fact.

We integrate DNN with legacy systems. We integrate DNN with BusinessObjects XI and Crystal Enterprise 10. We integrate it with barcoding, rfid, handheld devices, call centers, real estate, etc. If you can code it, it can be added to DotNetNuke, given the proper time and/or budget.

For example, we integrated Crystal Enterprise administration within the DotNetNuke portal software. It is seemless to both the user and the administrator. As you could guess, it all runs off of roles. Yes we had to modify the core, but in the end it was built for a specific user and we were even able to easily upgrade to 3.1.1 before we deliver in a week.

We are wrapping up a two year project October 31st, 2005. Integration with legacy data sources from multiple sources, reporting, business intelligence, and a host of other items for the Department of Defense. The price tag was over $1 million per year. We slashed past any bounds we thought the software might have and exceeded expectations.

To me the question isn't what can DNN not do, but what can I not do. DotNetNuke is a starting point for me. Anything beyond that is only limited to what my mind can think and what the framework can handle, and there is always ways around the framework for the dreamer....

Sowens

First, congratulations on you and yours achievments.

I think Melinda, "real hard" might mean doing a lot of what you are mentioning.  Expecially since she may not have a team.

I know for sure it can't make the coffee in the morning .

Other than that either pages can be made into ascx pages or wrapped in them and added to make them "look" like they are a part of DNN.

nitro001 wrote:

I know for sure it can't make the coffee in the morning .

Ever hear of X10, PLC, or even serial devices?  It CAN make coffee!  Just like anything else, you just need to add enough hardware and code...

I totally am working on a module to make DNN wash my car everyday but I'm having trouble finding the serial interface to my hose

RLyda wrote:

nitro001 wrote: I know for sure it can't make the coffee in the morning . Ever hear of X10, PLC, or even serial devices?  It CAN make coffee!  Just like anything else, you just need to add enough hardware and code...

Da power of the X10

http://www.komar.org/cgi-bin/halloween_webcam