Easy .NET web development?

Question

I am currently working on a project that has a significant amount of both client and web code. Client code is written in C #, and the web fragment is written in PHP. Maintaining consistency between the two worlds is becoming cumbersome, and I want to consolidate .Net web code.

The problem is that I hate web development in ASP.Net Web Forms. I want something as raw as PHP, just using C #. I got a little familiar with ASP.Net MVC, but it looks like it is too much abstracting the query logic to your liking.

Does anyone know an easy way to allow C # + .Net to handle web requests? Should I look more closely at MVC?

Update: I went with ASP.Net MVC, and so far I am very pleased.

Answer 1

If you want to get away from ASP.NET Web Forms, I recommend ASP.NET MVC with a custom view engine (like Spark or NHaml). This will give you the consolidation you are looking for and avoid most web forms that you don't like.

AFAIK, in order to do .NET web development, you will have to interact with ASP.NET in one form or another, but custom viewers in MVC may be the abstraction you're looking for.

Answer 2

Now you can use the software stack, completely divided into IIS and ASP.Net, using Kyak, Nancy and Gate.

http://bvanderveen.com/a/gate-0.1.0/

Answer 3

You might want to check out Kayak , which, to my knowledge, is the only standalone .NET development environment that is not ASP.NET.

Caution: implementing request processing on kayaks is not the best, so performance or scaling problems may occur. I can’t say for sure - I just read it, not run it.

Edit: I took another look at the source code, and it looks like they rewrote a significant portion of their server code and thereby fixed the underlying problems. Efficiency is probably not going to be a problem.

Answer 4

MVC.NET is open source, so you can get it to do what you want. This is a framework that can be redefined, expanded, etc. I would look at him closer. It works great for me, and I came amid CGI, Struts, and Webwork. I like it.

Answer 5

In my opinion, nothing is easier than combining NancyFX (http://nancyfx.org/) with Dapper (https://github.com/SamSaffron/dapper-dot-net) to access the data.

NancyFX can be hosted in ASP.NET, WCF, Azure, OWIN-compatible environments, Umbraco, or you can write your own host.

Also read the following articles: http://theothersideofcode.com/lightweight-development-in-dot-net-nancy http://theothersideofcode.com/lightweight-data-access-in-dot-net-massive

I also suggest you TinyIoC (https://github.com/grumpydev/TinyIoC) to decouple your application tiers.

Regards, Giacomo

Answer 6

You should learn about IHttpHandler and IHttpModule . This is the foundation for ASP.NET WebForms. Brad Wilson has a good introduction to the first.

In the bad days, when WebForms was an ASP.NET development method, I wrote my own MVC framework with these interfaces. The bit that I was struggling with at that time was the View engine, but now there are several.

Take a close look at ASP.NET MVC, as the source is available and will resolve itself. Perhaps you want to change some of the conventions used, not the whole structure.