I've felt the same way generally. I have an ASP Classic Site (who's design
isn't that complex) that I have tried for two months to replicate using
ASP.Net. After two months I have only duplicated the "public" part of the
site which doesn't require any authentication.
I can't get anywhere with the "administration" part of the site that
requires user authentication. MS only provided an SQL "Membership Provider"
that requires SQL Server be loaded on the Web Server which *won't* be there
on the hosting web server (and even if it was I wouldn't want to use it). So
I have fought and fought to create a provider for an Access "MDB" Database.
Every "example" I have tried to employ (some by MS, some not) fails. With
ASP Classic it took a Session Variable and a couple lines of code that can
be done in Notepad and works perfectly and I could almost do it in my sleep.
So the "production" site continues to remain ASP Classic.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
Ashe Sjedic said:
In asp , you make a query string with one line.
Now you have to click click click, add parameters edit templates
dig thru the documentation
type bunches and f*&^(cking bunches of code to just come up with
item.asp?orderID=xxxx
what the F$$cking FD*ck is this F&&ck sh(*********t?