This project is read-only.

Nice system! First request: LINQ to EF

Dec 8, 2008 at 5:28 PM
Is that in the plans anywhere? :)

P.S. -- Good job, folks!

P.P.S. -- First! :)
Dec 8, 2008 at 5:52 PM
It is and it isn't.  We've gotten feedback already that an EF provider would be a good thing.  We built a provider model for data providers so it shouldn't be too hard to move it to EF, but I'm honestly not super familiar with EF having not used it yet, so there may be some major changes needed.

The EF team has actually shown (verbal) interest in building an EF provider for us to help show it off.  I will be emailing them today to see if they still have interest and will post back to the discussion about what I find out.
Dec 9, 2008 at 12:04 AM
I second this.

I really want to get familiar with EF more in production environments and seeing if it is ready and capable. This would be a great proof of concept.

Also, can this be deployed to a shared hosting environment? I hate to bring up competitors but ASP.NET lacks in quality CMS's out there to compete with Drupal, Joomla and such.

I know there is DotNetNuke but the UI for DNN is horrendeous. Drupal and Joomla are top notch. I've tried some commercial ASP.NET CMS's to see how they compete against Drupal and Joomla however they don't compete very well. They rarely install well in shared hosting providers. DNN does this well however.

Unfortunately ASP.NET doesn't compete too strong in this category except really expensive sites where people can afford a $1000+ license for a CMS.

Sorry for the rant but I see big potential here.

I really like the providers concept. I think 2 things would be huge for this, modules concept and an extensible account/role/security concept. This would allow a lot of things to be built ontop. Perhaps a community portal for contributed modules would be great. Drupal has a great community for this.

I have been wanting to use an ASP.NET CMS for a long time now but DNN just didn't strike me as what I wanted. I talk to Java/.NET developers all the time and nobody has liked DNN but its usually the only option if your forced to go .NET.

If this CMS could get some key things like a web installer in hosted situations and some building blocks for extensibility we really have a compelling project here :)

Sorry for all the words. I am really excited to see a real clean ASP.NET CMS project!
Dec 9, 2008 at 3:35 AM
I am a joomla CMS user, but I am a dotnet developer, so I like this project.
Dec 9, 2008 at 3:58 AM
Synced - Have you tried Umbraco
Dec 10, 2008 at 3:55 AM
I tried umbraco awhile back. It seems too developer centric. Although I am a developer, setting up a website shouldn't be all development tasks. Joomla and Drupal do a great job of letting the average joe create a rich website.

Perhaps I didn't give umbraco a good enough chance.

I never really was able to find a good umbraco community of modules and groups of people working on extending it like you see for Joomla, Drupal and DNN.

Drupal and Joomla are first class. ASP.NET needs something of this calibur badly in my opinion.
Dec 10, 2008 at 6:29 AM
I've tried dozens of commercial and open-source .NET CMS solutions: Umbraco, Kentico, DotNetNuke, Sitefinity, and the obscure one-off variations from Lots of them bombed because they required full-trust. Thus, I settled with Community Server Express, as most of it can run in medium-trust and has all the functionality I need for the sites I'm pushing.
Dec 10, 2008 at 12:59 PM
I think with every release Umbraco comes closer to the Php CMSes, having used it for several project I must disagree with some of your remarks

to start you only need to install 1 website and maybe one of the sample site packages to learn how it works
its community is large enough - you'll find a lot of useful info at the Umbraco forum and for most features you can find extra packages and examples
with good knowledge of Xslt you can very quickly set up a custom website
it's true it requires Full trust to run it, but there are some hosting providers that will allow this (although you could argue that's not a good security practice)

the real drawbacks to me 
no workflow features yet, no authoring checkin/checkout
some features in the UI don't work well unless with IE, which is really a pity for an open source project

still, I'm very curious about Oxite, especially since it showcases the new ASP.Net MVC framework and it's an initiative from MS people

Dec 13, 2008 at 7:57 PM
Designers shouldn't need to know XSLT though.

Also I'm not a big fan of the UI in umbraco. Not a big fan of treeview panel navigation to be honest. Drupal and Joomla have a rocking administration backend interface.