dotnetnuke experience

[dmm]

hi all,

I am completly new to the world of ASP and am after some advice.

I have been given a requirements document that reads suspiciously like a
portal solution with added bells and whistles. I have heard good things of
dotnetnuke and I wanted your thoughts on it such as:

-Cost/benefit of going with it over rolling my own using 2.0 (for the built
in roles stuff). The CMS is important, but not the only functionality I need
to give them.
-Issues with usage on public (likely shared) hosting platforms
-Integration with nuts and bolts site functionality ie not just the
presentation bit - for example enquiry forms writing to my DB and sending an
email, admins viewing cutstom pages.

Any thoughts would be very much appreciated

[Ray Booysen]

dmm wrote:

hi all,

I am completly new to the world of ASP and am after some advice.

I have been given a requirements document that reads suspiciously like a
portal solution with added bells and whistles. I have heard good things of
dotnetnuke and I wanted your thoughts on it such as:

-Cost/benefit of going with it over rolling my own using 2.0 (for the built
in roles stuff). The CMS is important, but not the only functionality I need
to give them.
-Issues with usage on public (likely shared) hosting platforms
-Integration with nuts and bolts site functionality ie not just the
presentation bit - for example enquiry forms writing to my DB and sending an
email, admins viewing cutstom pages.

Any thoughts would be very much appreciated

We use Dotnetnuke as our website. Its a pretty good system and handles
most of what you need and whatever is missing you can just roll your own
as a seperate module.

It has a complex system to handle modules so have a play around first
and develop a simple module first.

Regards
Ray

[gerry]

hi ray
what is your opinion regarding performance ?
we did look into dnn a little while back but it seemed like even a simple
stock personal website was a real dog and tended to consume mucho server
resources.
also , which version are you using ?
Just asking as I am considering a second look at this now that they have a
..net 2.0 version out.
Gerry
"Ray Booysen" <rj***********@ rjb.za.net> wrote in message
news:OK******** ******@TK2MSFTN GP02.phx.gbl...

dmm wrote:

hi all,

I am completly new to the world of ASP and am after some advice.

I have been given a requirements document that reads suspiciously like a
portal solution with added bells and whistles. I have heard good things of dotnetnuke and I wanted your thoughts on it such as:

-Cost/benefit of going with it over rolling my own using 2.0 (for the built in roles stuff). The CMS is important, but not the only functionality I need to give them.
-Issues with usage on public (likely shared) hosting platforms
-Integration with nuts and bolts site functionality ie not just the
presentation bit - for example enquiry forms writing to my DB and sending an email, admins viewing cutstom pages.

Any thoughts would be very much appreciated

We use Dotnetnuke as our website. Its a pretty good system and handles
most of what you need and whatever is missing you can just roll your own
as a seperate module.

It has a complex system to handle modules so have a play around first
and develop a simple module first.

Regards
Ray

[Ray Booysen]

I haven't used version 4.x (the asp.net 2.0 version) but it shouldn't be
a hog on resources. In fact I run a copy on my laptop for development
purposes without a problem.

I'm currently using version 3.2.0.

Let me know if you need any other help! :)

Regards
Ray

Igerry wrote:

hi ray
what is your opinion regarding performance ?
we did look into dnn a little while back but it seemed like even a simple
stock personal website was a real dog and tended to consume mucho server
resources.
also , which version are you using ?
Just asking as I am considering a second look at this now that they have a
.net 2.0 version out.
Gerry
"Ray Booysen" <rj***********@ rjb.za.net> wrote in message
news:OK******** ******@TK2MSFTN GP02.phx.gbl...

dmm wrote:

hi all,

I am completly new to the world of ASP and am after some advice.

I have been given a requirements document that reads suspiciously like a
portal solution with added bells and whistles. I have heard good things of dotnetnuke and I wanted your thoughts on it such as:

-Cost/benefit of going with it over rolling my own using 2.0 (for the built in roles stuff). The CMS is important, but not the only functionality I need to give them.
-Issues with usage on public (likely shared) hosting platforms
-Integration with nuts and bolts site functionality ie not just the
presentation bit - for example enquiry forms writing to my DB and sending an email, admins viewing cutstom pages.

Any thoughts would be very much appreciated

We use Dotnetnuke as our website. Its a pretty good system and handles
most of what you need and whatever is missing you can just roll your own
as a seperate module.

It has a complex system to handle modules so have a play around first
and develop a simple module first.

Regards
Ray