Hi everyone!

In our company we are getting ready to start developing a web application. We have been using DNN for quite some time now and we like the way it works. We have built some smaller and simple modules. The features that DNN core provides come in handy. But this time we are thing of using the DNN core for a bigger web application. By doing this, we would not have to worry about things already built in DNN such as mail sending, users management, error handling, modules and much more.We could realy focus on the application we are developing. But i have worries. Is it better to start from scratch and make a new core? Are we going to be limited by the DNN core? This application would not be only a single module. It would have many modules and they need to comunicate. Is there an easy way to do this? We would not like to modify the core so we could use the standard upgrades provided by DNN. What do you people think? Is this a god idea or should we start at the beginning.

Thanks a lot for helping us out!

In addition to Michael's comments, why would you want to reinvent the wheel?

As with any large project there will be a learning curve, but once you get your feet wet the ideas will start to flow and you'll find yourself being very productive. As far as communicating between modules, you might consider the design and implications of such activities. Real time communication and state handling is possible, but rarely worth the effort. Often similar behaviour can be implemented through data in the database itself, it really depends on your requirements.

Finally, don't forget the team of DotNetNuke enthusiasts that are here in the forums. They are always willing to lend a hand and share their experiences.

Good luck on your project!