Anthem vs Ajax.net

[tshad]

I am rewriting my VS.Net code to convert from .net 1.1 to .net 3.5 (VS
2008).

Now that Ajax is part of the VS, I was curious if it is better to use
Ajax.net or is Anthem still a better bet?

I liked Anthem before but we are using Ajax.net at work and may use it just
to get more familier with it. But that is not necessary.

Thanks,

Tom

 

[Cowboy \(Gregory A. Beamer\)]

Either is fine. I would, personally, examine the built in stuff, as it will
get more full featured over time (already has with SP1). But, if you have
already invested a lot of time with Anthem, you have the learning curve
licked. If it fulfills all your needs? Just my two cents.

 

[tshad]

Either is fine. I would, personally, examine the built in stuff, as it
will get more full featured over time (already has with SP1). But, if you
have already invested a lot of time with Anthem, you have the learning
curve licked. If it fulfills all your needs? Just my two cents.

I agree.

I had used anthem for a couple of years but haven't used it for over a year.

I am setting up some new stuff using VS 2008 and was trying to decide
whether to go in the direction of Ajax.net or use the newer version of
Anthem.

The problem with Anthem seems to be support and I don't know if it works for
2008 or not and they are now trying to decide which direction to go from
what I read on the SourceForge site. Someone else has been supporting the
new version but doesn't have time to work on it and is looking for people to
help. There is someone else who has rewritten it and is going to be putting
it out soon.

I really liked Anthem before but now that MS has it in 2008, the question is
should I go in that direction or not. That would depend how good it is at
this point.

Since I am just starting the project, I can go in either direction.

Thanks,

Tom