Thanks!
When buildin sites I am used to build every part my self from scrath, this is good when I need to make costumizations like The one i mention in point 1. To move to a CMS system like DotNetNuke is ofcourse a big step, but I see that it could save me alot of time.
1. Probably I will have to customize every module I am using to be able to make a costumization like this. This is ofcource not impossible but it will demand that I have the souce code for the modules and ther will probably not be any updates to new version becource it will involve alot of work(to move costumizations).
But if the version I am building on works, no update should be necessary.
2. Grate!
3. Grate!
4. Ok
There is a couple of "problems that I see
A. The source code is VB.NET and ofcource I can manage this, but I always work in C# when writing new stuff. This will result in a mixed code base which is not vary professional if the site was to be sold one day.
B. The structure on the DotNetNuke solution look very simple, it is not a layered solutuion which I would have hoped for.
C. When the site become costumized there is no way to simple update the codebase, this could maby have been alot easier if the solution was some kind of layered solution.
I did not choose the DNN 5.x version becourse it simes like people hav alot of problem with this version?