Linq to Sql vs Nhibernate vs SubSonic vs Stored Pr

Question

I am looking to develop a website for a news channel.

So, Obviously its gonna receive a lot of hits daily and will be updated a lot on daily basis..

I have experience in ASP.Net and SQL Server..

These are the technologies i am considering to work with. Please help me choose the right method considering the amount of load it will take..

Technology??

1) ASP.Net Webforms

2) ASP.Net MVC 1.0

And data access??

1) Linq to SQL (Impressive but rumours say Microsoft is abandoning it)

2) Linq to Entities (Performance issues)

3) Datreader/Dataset

4) SubSonic (No idea)

5) NHibernate (No idea)

Please explain your point while leaving your comment..

Thanks

Chitresh

Answer 1

I'm just developing something and was at the same crossroads you are now. If you're a seasoned developer I suggest you go with Asp.net MVC. Overall I've had a great experience with it.

Considering your DAL it's a bit more tricky.

We did choose to go with LINQ to Entities (since L2SQL is abandoned), but we ended up using custom T4 templates that generate code out of EDMX file. It works great and we have all the possible customisation we need. But if I had to choose now, I'd probably rather go with either Subsonic 3 (because of the LINQ to DB support and T4 generator) or Fluent nHibernate. I know Subsonic isn't probably going to deliver exactly what I would need, but I'd be able to customize the templates. nHibernate on the other side doesn't support LINQ to DB which was something of my preference.

Edit If you ask me: LINQ to Entities is basically LINQ to SQL with additional mapping to custom types. Ok. There are alyo some minor differences but in general that's what it is. And it seems natiral that MS is abandoning it.

Answer 2

If you want a simple clean design thats fun to implement and extend in the future ill go with asp.mvc and entity framework. I would start out with the movie database video tutorial off of the asp.net mvc website.

Answer 3

If I were you I would use LINQ to SQL without fear of Microsoft "abandoning" it. First, Microsoft isn't abandoning LINQ to SQL they're creating another path for it for the purposes of allowing other vendors (Oracle, DB2, etc) to LINQ into it so-to-speak. I have read several posts by key members of the LINQ team and they will continue making modifications to LINQ to SQL and the migration path from that to their newer tool will be easy. Second, LINQ to SQL is soooo easy to use with the data context. If you know SQL then learning LINQ isn't too difficult.

As far as which technology to use, 1) ASP.Net Webforms or 2) MVC: my answer is that they're not mutually exclusive. Webforms can be built on top of the MVC model or not. It's up to you whether or not you use MVC. If you want your website to be completed quick and dirty, I would probably skip MVC. If you want your website to be easily extensible in the future and/or allow graphic designers to make changes to the design without messing up code then I would implement MVC.