Are there any DotNetNuke developers that are still alive?
-
Because the 20+ minutes it takes to build is making me suicidal! How was this thing ever developed in the first place?
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)IIRC, it was based on the old IBuySpy implementation, and it spiralled out of control from there. A couple of years ago I bought the Wrox book on it, and it was awful. It was written by the guy who started it off, and he spent all his time congratulating himself on how wonderful DNN is. (Why do I keep getting reminded of Duke Nukem whenever I see DNN?)
Deja View - the feeling that you've seen this post before.
-
IIRC, it was based on the old IBuySpy implementation, and it spiralled out of control from there. A couple of years ago I bought the Wrox book on it, and it was awful. It was written by the guy who started it off, and he spent all his time congratulating himself on how wonderful DNN is. (Why do I keep getting reminded of Duke Nukem whenever I see DNN?)
Deja View - the feeling that you've seen this post before.
-
Anything else you can suggest? Any extensable .NET based (preferably C#) CMS would do.
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008) -
Because the 20+ minutes it takes to build is making me suicidal! How was this thing ever developed in the first place?
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)Curious, what kind of changes do you have to make where you have to recompile the core? The last time I had to rebuild the core, it did not seem to take that long. Version 4.5 was the last one I used, but still have several sites running on it.
Rocky <>< Blog Post: Domain Auction August 1st! Tech Blog Post: Microsoft Live Writer Plug-ins! Photo Stuff Blog Post: CHDK Motion Detection and other stuff - Quick notes!
-
Pete O'Hanlon wrote:
The lads are currently reviewing it for me
Ooohhh!!! Get you!!!!! :-D
Recent blog posts: * SQL Server Memory Usage * Monitoring change in XML data * Debugging into the .NET Source code My Blog
-
Pete O'Hanlon wrote:
The lads are currently reviewing it for me
Ooohhh!!! Get you!!!!! :-D
Recent blog posts: * SQL Server Memory Usage * Monitoring change in XML data * Debugging into the .NET Source code My Blog
Colin Angus Mackay wrote:
Ooohhh!!! Get you!!!!!
Now - do that in an Alan Carr voice and say it out loud.
Deja View - the feeling that you've seen this post before.
-
Because the 20+ minutes it takes to build is making me suicidal! How was this thing ever developed in the first place?
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008) -
Curious, what kind of changes do you have to make where you have to recompile the core? The last time I had to rebuild the core, it did not seem to take that long. Version 4.5 was the last one I used, but still have several sites running on it.
Rocky <>< Blog Post: Domain Auction August 1st! Tech Blog Post: Microsoft Live Writer Plug-ins! Photo Stuff Blog Post: CHDK Motion Detection and other stuff - Quick notes!
I am developing a small module that consumes a web service. So when the web service needs to be updated, the whole site seems to recompile... I also tried making a library for the web service client, but as soon as the assembly gets updated, DNN recompiles itself in it's entirety! I am using VS2008.
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008) -
I am specifically talking about extending, and the pain that goes with that. Once it runs, it runs fine, but I cant wait 20 minutes for the site to compile every time I make a tiny change.
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008) -
Pete O'Hanlon wrote:
The lads are currently reviewing it for me.
Care to enrich me with some info too?
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)Well - so far they haven't reported any major issues. It seems extensible enough, and relatively stable.
Deja View - the feeling that you've seen this post before.
-
I am specifically talking about extending, and the pain that goes with that. Once it runs, it runs fine, but I cant wait 20 minutes for the site to compile every time I make a tiny change.
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008) -
Pete O'Hanlon wrote:
Joomla[^] is supposed to be OK.
You got me all excited only to find out Joomla runs on PHP... :doh:
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)OK - if ASP.NET is your criteria, there's always Kentico CMS - although you have to pay for this one.
Deja View - the feeling that you've seen this post before.
-
Because the 20+ minutes it takes to build is making me suicidal! How was this thing ever developed in the first place?
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)The way we had it implemented, it would not have to compile the core more than once. Ever. The things that did compile were the DNN website, which references the DNN libraries, and our custom modules, which we wrote in C#. We had one VS solution that was the core, and one VS solution that had the website and custom modules in it. We worked really hard to not modify the core, or at least keep our changes documented and short so that when the next version came out (which it did about every 6-8 weeks), we could upgrade without any problems. I would suggest trying our solution to your problem: splitting up your VS solutions into core DNN libraries and the website with custom modules.
Success is the happy feeling you get between the time you do something and the time you tell a woman what you did. --Dilbert My left name is Tremendous Savings, Ms. America – Señor Cardgage
-
Because the 20+ minutes it takes to build is making me suicidal! How was this thing ever developed in the first place?
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008) -
OK - if ASP.NET is your criteria, there's always Kentico CMS - although you have to pay for this one.
Deja View - the feeling that you've seen this post before.
-
The way we had it implemented, it would not have to compile the core more than once. Ever. The things that did compile were the DNN website, which references the DNN libraries, and our custom modules, which we wrote in C#. We had one VS solution that was the core, and one VS solution that had the website and custom modules in it. We worked really hard to not modify the core, or at least keep our changes documented and short so that when the next version came out (which it did about every 6-8 weeks), we could upgrade without any problems. I would suggest trying our solution to your problem: splitting up your VS solutions into core DNN libraries and the website with custom modules.
Success is the happy feeling you get between the time you do something and the time you tell a woman what you did. --Dilbert My left name is Tremendous Savings, Ms. America – Señor Cardgage
This is the way a large project I'm working on is structured. The only time we need a whole recompile is when interfaces or web service method signatures change between projects.
Todd Smith
-
Anything else you can suggest? Any extensable .NET based (preferably C#) CMS would do.
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)How do you know when CMS stands for Customer Management System vs. Content Management System?
Todd Smith
-
Pete O'Hanlon wrote:
although you have to pay for this one.
US$20 000 is a tad much! ;P
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)Here's an ASP.NET CMS I found out about recently: http://www.sitecore.net/Products/Sitecore%20CMS.aspx[^] No mention of price though... could be more than 20k, could be less :doh:
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
CP article: SmartPager - a Flickr-style pager control with go-to-page popup layer.