I’m developing a data access component that will be used in a website that contains a mix of classic ASP and ASP.NET pages, and need a good way to manage its configuration settings.
Is there a way to share cookies across different domains and different applications (classic ASP and ASP.NET)
After going through a number of different articles and not finding anything especially conclusive that takes me step-by-step through the process, I’ve come seeking help.
A client uses classic ASP to log in to their web based backoffice.
We are migrating an ASP Classic website over to ASP.Net. One of the big hurdles is the large amount of data stored in SessionState by the ASP Classic website.
Why is it that ASP/ASP.NET Response.Redirect uses a HTTP-302 status code (“Moved Temporarily”) even though in most cases a HTTP-301 status code (“Moved Permanently”) would be more appropriate?
In a previous job we had a classic ASP application that no one wanted to migrate to ASP.NET. The things that it did, it did very well.
We have a website in classic asp that we are slowly migrating to ASP.NET as necessary.
In webform/mvc we can use script and links as,
script src=” Url.Content(“~/Scripts/util.js”)”
I have a public facing hobby site that gets about 3000 unique visitors a day, written in classic ASP that is in bad need of a revamp and redesign. I’ve faced the realization that an upgrade to ASP.net is the best way to go to implement features that are just too hard in ASP for the hobbyist (consuming RSS feeds, authentication and user profiles) but which I’m keen to get stuck into once I get past the redesign/upgrade.
