Mike Grace wrote
Q1) Is the only way to add bespoke content to a DNN site via modules?
I am unfamiliar with "bespoke". But generally adding/displaying content to a DNN site is through modules. Skin objects can behave similarly in many ways, but are less flexible.
Q2) I use Component One dataobjects and controls in other ASP.NET projects. The modules that I create will be for
inhouse/corporate website use only. I will not be selling them.
How easy is it to completely ignore the DAL/BL layers and use my own data access?
Unfamiliar specifically with Component One, but its fairly easy to make your own data access, especially if you aren't distributing them. You would just write your data access as you would in any traditional ASP.NET app. (Although arguably providers may be the way traditional apps go in the future.).
Q3) Am I limited to view/edit functionality or is it possible to have a view, then multiple edit screens with its own menu i.e. to create a mini application within a module?
You can any number of functions (views/edits) in your modules just like any ASP.NET control. There are a couple of ways to implement them which have more or less integration with DNN security. You can make multiple controls that are invoked by different keywords and stored in module definitions. You can display these in a DNN traditional way by using the ModuleActions collection (see some of the core modules for info on this). You can also have multiple edits available through using asp:panels and your own scheme as to when to display them.
Sorry for the dumb questions but I am really trying to find my feet. DNN does everything else I could wish for without me having to reinvent the wheel. Good work.
Its definately a great launching point for a web app of just about any scope.