Don’t use .asp in a production environment. It will not stand up to the pounding.

(If you’re using .aspx, i.e., the most fancy-schmancy up to date stuff from MS, it may be a different story. I dunno about that.)

Classic ASP is a magnificently enjoyable toy, and you can prototype things on it, but it’s not scalable past a very low point. I couldn’t get a stable BNN build using classic, and that was with traffic volumes of less than two or three thousand a day. It’s like building a functioning automobile with Lego bricks - it’s probably doable, but it’s likely not going to be a very good car.

If your client is planning to fail, er, stay small, then maybe you could get away with it. Or if you hate them, and want to leave them with something that works just fine until they get popular and then boom. And then you could recode it properly and charge them a second time.

But that, of course, would be wrong.

The boys over at Q&O have their own package that is in asp.

Here it is.

I suggest you ask my kids godfather.  Or better yet, I’ll ask him for you.

The godfather suggests:
Moveable type can be installed on Windows:  http://www.movabletype.org/documentation/installation/windows.html

...the only drawback is that it only runs against the MySQL database (whereas MS SQL Server is more standard an ASP environment).

Most of the .NET (Geeky software) bloggers that I read use something called SubText: http://www.subtextproject.com/

I hope this helps,

Robert stole the spirit of my reply, which was going to be, “Run away screaming.”

But then, I have that impulse whenever EE comes out with a new build, and my host isn’t Windows.

Resist the Dark Side, Luke.

Just so y’all know, the host is shared server space, so I don’t have admin access to add services that aren’t already running on the box. I’m not sure if it supports MySQL or PHP, so I’ll have to ask the hosting company.

I’m going to check out that package that Q&O is running on, though, and SubText looked interesting, too.

A lot of hatred of .asp in here. I used to work in a purely Windows company and all of our development was in .asp. From my point of view, it seemed awfully scalable and hardy. Frankly, though, in this instance I just need quick, easy, and easily customizable. The network load is going to be fairly low and their needs are, shall we say, modest.

No hate, man - I love ASP. One of the best things MS has done. It’s lots of fun to work in. It is scalable and hardy up to a point - it’s just that the point is too low for big sites. But you’ve got no real error handling and the client can’t interrupt the server - one bad process can hang your whole site up.

If your client just needs some code snippets fast and easy for a low-load application, then go crazy. I got the impression you were going to be implementing a full-bore CMS.

Hate leads to the Dark Side ... so I prefer to think of it as disgust rather than hatred ...

My reaction was due mainly to the troubles I’ve seen in the EE user support forums where people have been trying to run EE on a Windows server. I think servers should be left to the geeks to set up and run, and Windows should be left to us non-geeks. (I’m not a geek, I tell you! I’m not I’m not I’m not!!!)

Though, I did have a bad experience with .asp as a result of a .NET update on my XP machine.

Based on what I have read in this thread I would go even further and say that discussion of this nature should be left to professionals.