Asp

[DaveP]

I'd like to learn asp, firstly to try and develop my own site. And if I enjoy/become good maybe offer it as a business service/product.

But before I get to carried away with the idea, I need to learn it.

Can anybody recommend good books for beginners etc or an alternative.

 

[EqualOpportunities]

I'd like to learn asp, firstly to try and develop my own site. And if I enjoy/become good maybe offer it as a business service/product.

But before I get to carried away with the idea, I need to learn it.

Can anybody recommend good books for beginners etc or an alternative.

This any good?

 

[themistry]

I'd like to learn asp, firstly to try and develop my own site. And if I enjoy/become good maybe offer it as a business service/product.

But before I get to carried away with the idea, I need to learn it.

Can anybody recommend good books for beginners etc or an alternative.

You mean ASP.NET, not vanilla ASP right?

Bit of a shock to the system if you come from php/asp/perl/ruby.

You want to hit the ground with the latest incarnation (3.5) using MVC style development.

TM

 

[Jaws]

This any good?

That was the first Classic ASP book I read, it was a good and easy to follow book.

For ASP.NET the Core Reference book is very good. Not so sure on a beginners guide though.

 

[DimPrawn]

For a simple site, you might be better off with PHP.

ASP.NET is heavy going for a beginner with no .NET background.

ASP (classic) is long dead.

 

[bogeyman]

For a simple site, you might be better off with PHP.

ASP.NET is heavy going for a beginner with no .NET background.

ASP (classic) is long dead.

Even for larger sites, PHP (5) is a better bet than ASP.NET 2.0 - especially where performance matters.

You can even develop PHP in Visual Studio now, (almost) seemlessly.

See: http://www.jcxsoftware.com/vs.php

I hated ASP, and my love has not increased with the .NET incarnation. It's borked, bloated and bastardised.

I find a good compromise if you're deving for Windows backends is to write webs services in .NET 2.0 in C# or whatever, and do the front-end tier in PHP5. Works a treat.

 

[DimPrawn]

Even for larger sites, PHP (5) is a better bet than ASP.NET 2.0 - especially where performance matters.

You can even develop PHP in Visual Studio now, (almost) seemlessly.

See: http://www.jcxsoftware.com/vs.php

I hated ASP, and my love has not increased with the .NET incarnation. It's borked, bloated and bastardised.

I find a good compromise if you're deving for Windows backends is to write webs services in .NET 2.0 in C# or whatever, and do the front-end tier in PHP5. Works a treat.

I love .NET and C# to bits, but many aspects of ASP.NET 2.0 are very poor indeed, making real world Internet dev (as opposed to "look it's a datagrid for your Intranet again") very difficult.

I tend to ignore many of the "wizzy" asp.net controls but use the framework and some libraries of .NET code to create sites in a cleaner, SEO friendly way.

Your idea of PHP front end and ASP.NET web services sounds like a good idea.

 

[lilelvis2000]

You mean ASP.NET, not vanilla ASP right?

Bit of a shock to the system if you come from php/asp/perl/ruby.

You want to hit the ground with the latest incarnation (3.5) using MVC style development.

TM

MVC is sooo completely bizarre. Just recently sat through a session on it and found it confusing. Think you might want to stay away from it at the start.

ASP.Net is really a bad web page development system. But as I've been working with M$ all my career...I have stuck with their stuff....I still use classic ASP. ASP->ASP.net is like going from C++ to SQL. It turns you inside out.

Does PHP work with IIS? If so I might just shift into that.

 

[themistry]

MVC is sooo completely bizarre. Just recently sat through a session on it and found it confusing. Think you might want to stay away from it at the start.

MVC is just 3-tier development following a RESTful approach. Few other bells and whistles in there.


I do agree its confusing at first, however try it out (demo project), get used to it, them form an opinion. It is a MUCH better and easier way to work, especially when you couple the model/data tier with LinQ

As for PHP on IIS.... well not in production i hope

If you want an easy development environment, do a search for XAMPP.

HTH
TM

 

[themistry]

Your idea of PHP front end and ASP.NET web services sounds like a good idea.

Sound slow, over complex, brittle and inflexible to me?

TM