.NET technology stacks for web apps

[minestrone]

I know someone with an old (profit making plan B) VB app which he wants to rewrite it as a web app while self training in .NET.

Basically he asked how to skin the cat and being a java person I told him I did not know.

I kind of said well I know there is nHibernate and nSpring which are ports of the standard way of doing it in java but don't really know how you would do the front end but I would imagine it would be an MVC framework.

Was I talking crap on this subject? What are the most common ways of doing 'standard' DB driven transactional web apps in .NET.

Cheers

[2BIT]

I know someone with an old (profit making plan B) VB app which he wants to rewrite it as a web app while self training in .NET.

Basically he asked how to skin the cat and being a java person I told him I did not know.

I kind of said well I know there is nHibernate and nSpring which are ports of the standard way of doing it in java but don't really know how you would do the front end but I would imagine it would be an MVC framework.

Was I talking crap on this subject? What are the most common ways of doing 'standard' DB driven transactional web apps in .NET.

Cheers

being no expert myself I would imagine an asp.net/c# code base and LINQ for your DB connections and semantic layer

[eek]

being no expert myself I would imagine an asp.net/c# code base and LINQ for your DB connections and semantic layer

Current method of choice would be an ORM (entity framework, nhibernate) for persistent storage and MVC for the asp.net level.

So mvc templates for the frontend
mvc containers calling business layer objects for the logic layer
orm for the database

In an ideal world you then have nunit for test around everything and some mocking system for everything else.

As its a plan b tho scrap the detailed plan above and use codesmithtools or something to generate a plingo start point CodeSmith Tools and create standard asp.net pages .

[thunderlizard]

These days, ASP.NET MVC front-end;

C# or VB.NET DLL for the logic (to all intents and purposes there's practically no difference between the capabilities of the two languages, but C# is the most popular)

Data access - slightly up in the air. NHibernate remains fine. LINQ-to-SQL was once the Microsoft standard, but is now being cold-shouldered. It's the Fredo Corleone of ORM. New Microsoft flavour of the month is Entity Framework.

Or you could just not bother with a separate data access framework. As an old, heretical but sensible developer fairly recently said, "you know, I don't actually mind writing data access code".

[2BIT]

These days, ASP.NET MVC front-end;

C# or VB.NET DLL for the logic (to all intents and purposes there's practically no difference between the capabilities of the two languages, but C# is the most popular)

Data access - slightly up in the air. NHibernate remains fine. LINQ-to-SQL was once the Microsoft standard, but is now being cold-shouldered. It's the Fredo Corleone of ORM. New Microsoft flavour of the month is Entity Framework.

Or you could just not bother with a separate data access framework. As an old, heretical but sensible developer fairly recently said, "you know, I don't actually mind writing data access code".

******' microsoft, why do they keep replacing things all the time!

The Two Forces at Microsoft

[eek]

******' microsoft, why do they keep replacing things all the time!

The Two Forces at Microsoft

Personally I think its because Linq was a crap but quick solution to the problem of database independence.

I'm sure it was designed by people who wanted to keep inline sql statements inside their code while being able to ignore questions about security issues.

[2BIT]

Personally I think its because Linq was a crap but quick solution to the problem of database independence.

I'm sure it was designed by people who wanted to keep inline sql statements inside their code while being able to ignore questions about security issues.

don't know enough but it seemed to me an improvement over ado or dao, never got into it but a guy I knew loved it for his webapps

[thunderlizard]

It's an ingenious solution to the problem of moving your business logic out of the database and into the business tier, while still writing it in SQL.

[2BIT]

It's an ingenious solution to the problem of moving your business logic out of the database and into the business tier, while still writing it in SQL.

wasn't that what you did with ADO?

[fullyautomatix]

Current method of choice would be an ORM (entity framework, nhibernate) for persistent storage and MVC for the asp.net level.

So mvc templates for the frontend
mvc containers calling business layer objects for the logic layer
orm for the database

In an ideal world you then have nunit for test around everything and some mocking system for everything else.

As its a plan b tho scrap the detailed plan above and use codesmithtools or something to generate a plingo start point CodeSmith Tools and create standard asp.net pages .

MVC or WebForms. Although MVC is very good for test driven application, Web forms are really good for RAD.