|
Editorial Review Product Description
DotNetNuke is a powerful open source framework that creates and deploys robust modules on the ASP.NET platform. Written by its core team of developers, this book will provide you with the tools and insight you'll need to install, configure, and develop your own stunning Web applications using DotNetNuke 4.You'll first gain an inside look into the history of this project as well as the basic operations of a DotNetNuke portal. You'll then find detailed information on how the application is architected and how you can extend it by building modules and skins. With this information, you'll be able to complete projects such as commercial Web sites, corporate intranets and extranets, online publishing portals, and custom vertical applications. What you will learn from this book - The latest features and functionality of DotNetNuke 4 for ASP.NET 2.0
- The best way to install DotNetNuke on the server
- Proven tips for managing and administering a DotNetNuke portal
- How to dramatically enhance your Web site's user interface using skins
- Techniques for extending the portal framework
- Ways to create a unique look for your porta
Who this book is for This book is for the nondeveloper or administrator who wants to dive into the exciting DotNetNuke framework. It is also for experienced ASP.NET developers who want to use DotNetNuke to build dynamic ASP.NET sites or create add-ins to DotNetNuke. Wrox Professional guides are planned and written by working programmers to meet the real-world needs of programmers, developers, and IT professionals. Focused and relevant, they address the issues technology professionals face every day. They provide examples, practical solutions, and expert education in new technologies, all designed to help programmers do a better job. ... Read more Customer Reviews (16) 
Ugg...
I am very disappointed with this book. As others have said, most of the content is already available on the Net. The install chapter is the same garbage that is in the install doc that you can download from the DNN site (that was last updated in 2006). Even though the title of the book is "Professional DotNetNuke 4.0" the install chapter is heavily focused on version 3. Guess what - if I wanted to know how to install version 3, I would have purchased a book on version 3.
Here is how the version 4 install instructions start: "This section focuses only on the differences between the v3.x and v4.x Install/Source installations. For more detailed instructions, see the appropriate section in the v3.x installation instructions." So you have to read the part about version 4, but are often referred back to the version 3 instructions. This is a book on version 4. It's just pure laziness that the install instructions for version 4 aren't complete.
Do yourself a favor and find a different book.
Good book, bad technology.
If you are unlucky enough to get tasked with working with this godawful technology, I guess you have one of two options:
1) Buy this book. It's far, far from being comprehensive, but it's enough to keep you treading water for awhile.
2) Get a new job. This is my personal recommendation.
Not too helpful
This book might be the worst software book I have read. The most helpful thing in the book is the appendix with dotnetnuke related links. The examples are lame and the content is scattered like a bunch of different people wrote sections in a vacuum. No flow.
Great Buy very Infomative
When I started with DotNetNuke a year ago I knew absolutely nothing about it.I bought a copy of professional DotNetNuke 4 read it cover to cover and it did wonders.It is very easy to understand it covers everything you need to know, and best of all it is a great reference even when you have experience with DotNetNuke.I still reach for this book to answer most of my questions.
Exactly What You Don't Need To Use DotNetNuke 4.x
This book is NOT for you if you need to seriously use DotNetNuke or if you are going to embark on custom module development.
This book is definitely for you if you want to know why Shaun Walker and the other core folks made certain decisions from 1.x through 4.x. This is only useful if you have to write a review or report on DotNetNuke for a magazine or blog.
I've been using DotNetNuke seriously since before it was DotNetNuke and I have read all the books written about DotNetNuke through version 4.x. Frustratingly, none of the books gets my recommendation and this particular book is at the bottom. This book is full of general explanations that do you no good if you need to use DotNetNuke.
This book is a shining example of the Achilles heel of DotNetNuke: it's a framework by architects, for architects.
If you want to see what DotNetNuke ought to be more like, get the XMod module (it's a third-party product and I'm not affiliated with it in anyway and I'm not going to give you a link to it, just search for XMod).
XMod is doing what DotNetNuke should be doing because XMod is a user's product. If you don't really want to make your own module or find that the documentation on customizing DNN just does not cut it -- get something like XMod. You'll still be using DotNetNuke but something like XMod is well documented and provides many duplicate features of DNN that accomplish functions similar to DNN but in a much, much more robust and usable way.
In the case of both DNN and XMod the "user" refers to a developer.
Don't let anyone fool you, DNN is a developer's product and you need to know a lot about all the web applicaiton technologies involved and ought to be able to use Visual Studio and SQL at a minimum.
But the nutty thing about this book is that it spends half its time speaking above the developer talking about architectural decisions and other esoterica that will not tell you enough to mimic the architecture or use the code unless you are already a DNN expert developer.
This book will drive you mad if you are a developer who is not afraid to compile a VS project and you are looking for an answer such as, "How do I just add a couple of columns to the Survey module table, a bit of extra business logic and a few cosmetic changes I need?" This book will only reiterate that DNN modules are scattered all over the place in this provider and that or this App_Code folder or that. And that DNN achieves an oh-so-wonderful but madingly obfuscatory 'separation of Church and State' architecture.
The rest of the time this book talks below the developer and gives worthless "For Dummies" information about how to use the various modules like Announcements and Links. For goodness sake Wrox, how in the world did you pass off such a disjoint amalgam of chapters?
DotNetNuke is a very good application framework. Today (Spring 2007) DotNetNuke 4.5 is the best starting point for your web application regardless of size or deployment. DNN blows the LAMP alternatives out of the water.
It remains to be seen if DNN will continue to be needed. My prediciton is "No". DNN is already being absorbed into .NET & Visual Studio and will continue to be absorbed. The only wildcard is the need for Microsoft to present the illusion of "Open Source". It is an illusion because in truth, Microsoft directly funds and virtually controls DotNetNuke. (Sorry, Shaun, it's a fact even you admit in this book. But it's okay with me and most DNN users.)
Even though this book spends and inordinate amount of time explaining "For Dummies" details, it does not provide enough to be useful! For instance, it tells yous about the editor and the discussion module and then promptly dismisses both as inferior to modules you ought to go download. So, you are left on your own to use a module that is not documented.
Trying to develop a custom module in any version of DotNetNuke is not for the uninitiated and chances are you bought this book because you are endeavoring to create a custom module. You would think this book would excel at providing assistance to the custom module developer. But alasit does not.
It is full of "we did this in version 3 because people wanted that in version 2, etc." rather than getting down and dirty into custom module development. Also the examples are incomplete snippets and only in VB.
I will conclude this epistle with a plea to Shaun and the Core: Stop writing books! Instead, provide thorough, updated online documentation, tutorials and private forums. I'd pay way more than the price of this book for a library of sample projects (And please in C#!) with tutorials and explicit instructions. For instance, take Michael Washington's tutorials. I'd pay for access to that type of resource if it were fleshed out a bit more, presented in a more organized fashion and included in-depth documentation and access to private forums to ask questions and get help when deadlines need to be met (on a pay-per-use basis if necessary).
Trying to follow an example in this book will drive you mad because it always leaves out all the REALLY IMPORTANT details like paths, settings, options, creating and configuring IIS for webhost sites versus localhost sites etc. Constantly the book says things like, "If your site is hosted, you'll have to do this part differently." REALLY!? Just HOW is it done differently!? THAT'S WHAT I BOUGHT THE BOOK FOR!
P.S. It is quite evident that few of the Core Team actually use DotNetNuke. The Core really needs to add some serious users to its ranks. Right now it is just a bunch of (very good) system programmers. System programmers we all know are topnotch in their areas of expertise but usually suck at knowing what makes an application a winner with the end users. The upshot is that we who do know the latter end up spending the bulk of our DNN time tweaking under, over and around the ugliness and clumsiness of DNN. This ugly clumsiness can be seen architecturally where too many times, when you need another of something you have to create a new modules and there is no way you (the developer) are going to let end users add modules to pages. So you end up not being able to use a module only because you cannot get "another" one without adding a new module to a page.
... Read more
|
