Last post Nov 30, 2005 03:11 PM by PurpleBox
Nov 30, 2005 10:56 AM|dstruve|LINK
Nov 30, 2005 11:00 AM|christoc|LINK
Nov 30, 2005 11:07 AM|J7Mitch|LINK
There is more on that topic here:
Nov 30, 2005 11:25 AM|mzns1|LINK
We are evaluating what effect ASP.NET 2.0 will have on some of the 3rd party controls we use, specifically Infragistics. The new controls in 2.0 may replace many of the control suite features.
ASP.NET 2.0 or SharePoint Web Services do not pose even a small threat to DNN. When you wrap your applications around the DNN framework you have a complete solution ready to go.
While the current core modules have lots of room for improvement they still represent more than what is possible in ASP.NET 2.0. You would be writing a lot of code to duplicate the same functionality. The next release of core modules, based on the project
forums discussions, should decisively put DNN over the top.
DNN 3.2, along with the coming bug fix release is an excellent platform for ASP.NET 1.1.
DNN 4.0+ is just the beginning. It will be months before larger sites can move to ASP.NET 2.0 and SQL 2005.
Anyone running DNN3.x on an Intranet site with 100, 500 or a 1000 users should confirm to the fact that "out of the box" ASP.NET 2.0 will not meet their needs for security, forums, modules and content delivery. ASP.NET 2.0 reduces the code needed to accomplish
the same tasks as 1.1, but that still translates to a tall mountain of code to duplicate DNN.
Nov 30, 2005 11:36 AM|iwonder|LINK
Nov 30, 2005 11:43 AM|jking078|LINK
Nov 30, 2005 11:48 AM|dstruve|LINK
I new someone was goign to say that "its the wrong question" but im just thinking about what someone told me. You know how some technologists can get so confident about their own opinions. And Ive learned that there is no value in saying "thats the
wrong question", even if the question may not be fair. There is always value is making sure you are able to answer it. That being said, I appreciate all your guys feedback, invalueable for sure and much more knowledgable than the person asking the question.
Nov 30, 2005 11:52 AM|dstruve|LINK
Nov 30, 2005 11:57 AM|iwonder|LINK
Totally agree. That's why I always try to frame those remarks with a rephrasing of what I believe is the real issue to discuss. I get those comments, too. So, I really understand what you mean.
Nov 30, 2005 02:18 PM|adefwebserver|LINK
Nov 30, 2005 02:35 PM|iwonder|LINK
Nov 30, 2005 02:54 PM|adefwebserver|LINK
Nov 30, 2005 03:08 PM|dstruve|LINK
Nov 30, 2005 03:11 PM|smummert|LINK
Nov 30, 2005 03:47 PM|PurpleBox|LINK
I have 3 major categories to decide wether DNN is apropriate:
Flyer/product page: Best done in ASP.NET 2 with masterpages/themes, tech savy clients get a link to the VWD download page to edit their site. N00bs are given a windows.forms app that updates their site over FTP with XML files. Perhaps a webservice
ClubSites/Small Shops/Dudes with no money: Go with DNN + custom modules. Both techsavy as beginner clients use the web interface to edit their site
Higly specialized sites/ Large online Shops: These websites will benifit when build on an architecture that is centred around the core business of the website. In this case DNN would have to be extended too much to be a benifit over building
from scratch. The general services needed to build your architecture are provided by ASP.NET 2.0 so there is no reason to drag DNN as an extra layer between your site and .NET. The core business oriented architecture will allow for better editing tools to
be writen. They are best written as Smart or Thin clients.
Whilst I was typing the previous I tought about this analogy with cars:
Websites are like cars:
Most websites are a piece of cardboard with a picture of a car on it and a kid making "vrooeemmm" sounds. If you are a believer, this will work. And it wil work as long as you don't drive it furter than 3 houses down the road.
DNN fits into this as a multi-purpose-all-terrain-all-wheel-drive vehicle. It has sockets to be able to plug anything on it. It weighs 3000 Kg but thats allright because it has a 5000hp engine. It comes in a large box 90% preassembled, With guidelines on how
to complete the remaining 10%. It will never behave like a ferrari because it wasn't built to be one. But if you wanted you could configure it to look like a ferrari. And everybody would believe it until you have to take it to a racing circuit.
Specialized websites are like racing cars. They are built for only one purpose: Racing. Some are even built to race on only one circuit. It will never behave like a truck. And even if I made it look like a truck you wouldn't use it as a truck becuase its a
racing car. It will beat the nuts out of our allterrain vehcle at racing because it was designed for it. But take it of the racing track and it becomes useless.
The point is a good site needs an architecture. DNN's architecture might not be the best you could have for your particular usecase. But at least it is an architecture, and a working one for the matter.
If you have money/time to build your own architecture, you should do it. If you can build your website in 10 mins in VWD you should do it. For anything else use DNN.
my 2 cents after working 1,5 years fulltime with .NET and DNN