In my spare time (is there ever any?) of the past couple of days I have been manipulating both the ASP.NET Starter Kits and the source code from DotNetNuke . Both frameworks seem to have their advantages and disadvantages but I really like the DotNetNuke stuff a lot. You can take this source code, install it on a web server, add the SQL Server database (or Access if you really must), make a few minor “adjustments” and you have a pretty cool looking web app in production. As I am not that 'graphically inclined' (my wife thinks I see everything in shades of grey), the skinning architecture of DNN is superior to the Community Starter Kits and with very little tweaking, you can completely overhaul the visual identity of the site. Furthermore, there are numerous skins available for DNN where as the Starter Kits only have a select few (although these can be modified, you still need a graphical eye as to what looks good). I will continue to use both in tandem in my quest to conquer ASP.NET, but DNN is worth a hard look.
ASP.NET Community/Portal Starter Kit vs. DotNetNuke
New on Geeks with Blogs
- Because of AI, You Need a New Development Team
Your existing team is buried in the complexity of your existing product. AI rewards the team with a blank slate. Most companies don't have one.
- The Offshore Problem That Starts With a "Yes"
The stories about offshore "not working" are rarely about skill. They are about an invisible communication gap, and it starts the moment someone says yes.
- The Focus Five: Five Questions to Know If Your Team Is Actually Making Progress
Almost nobody trains you to be an engineering manager. You were good at writing code, so you got handed more people and more meetings, and one day the job…
- Why Nobody Knows What Engineering Does
At VinSolutions, I was famous for one thing that had nothing to do with writing code. Every single time we shipped a release, I posted about it. On social…