Can an ASP page be used with a master page?
Do you still have this problem? There is a really old tool to help convert to an early version of .ASP. Unfortunately, I don't think this is the best practice for converting to more recent versions of asp.net. I am working on a project to transform a classic ASP application with many, many pages and still use records with an old SQL database. I found that getting the results of each "view source" page and creating a new page inside my VS2010, web project using the master page to keep consistent results across the site is very good.
The only problem is that this is very tedious and requires frequent testing to ensure that the page matches the old page.
Let's go back to the original problem of using Classic ASP in a new ASP.net application. I believe the problem can be solved with two app pools and two apps on webserver apps and linking to old pages as a link in an iframe. Just a thought ...
Greetings
a source to share
I do not think so. Are you talking about classic asp? I just found this discussion .
[change]
Maybe you can. Check this out.
[/ edit]
a source to share
I recommend creating a new ASP.NET MVC project (as opposed to WebForms) and converting all of your ASP.NET pages to ASP.NET in one exercise.
Doing a stepwise conversion and getting ASP and ASP.NET up and running will lead to headaches, and while it may be perceived as faster, the overall cost is likely to be higher than a one-time conversion.
ASP.NET MVC can convert from ASP much better than ASP.NET WebForms in most cases.
a source to share
I have this problem at the moment. Some ASP pages are so complex that changes to the functionality of the site are more important than the transfer of some of the more complex pages.
If you still have to work side by side, slowing them down does the following.
-
Get your business logic in a .NET assembly "tlbimp.exe" so that it can interact with ASP, and then move your page's solutions to communicate with that component. This way you can now exchange business logic and therefore be able to move the UI data.
-
Pass Session / QueryString data through the database, not by the query string. This means you have to pass the Session / QueryString data in XML or Key / Value pair and store it in the DB (with an expiration date). Then redirect your ASP with a GUID. Someone has the option to grab the session by grabbing the previous GUID. Therefore, run the scheduled task regularly to clear session data older than 1 minute.
-
When migrating to / from .NET, try making pages to do your operations before passing across boundaries. This way, pages can be ported more easily. For example, let's say that .NET displays an order and ASP searches for a product and adds it to its shopping cart. Make sure the operations are separate and do not pass the product through query string parameters. So you can do something like redirecting to the order page through the query string parameters - http: //...../Order.aspx? Id = (as long as your user has permission to view the order).
-
Make sure your ASP code uses stored procedures and not embedded SQL, as this means code reuse is easier.
-
I found that creating dedicated redirect.asp and Redirect.aspx pages is helpful as you can see the data flowing across boundaries - it's easier to debug, but you will hear a lot of clicks as custom ASP -> ASP_REDIRECT -> ASP.NET_REDIRECT -> ASP.NET ...
-
Globalization is a serious problem and has caused problems with our users. Changing the language and redirecting to / from the site in ASP sometimes resulted in their default language being translated to English and from English to Chinese!
There aren't really many ways to make the transition easier, it's mostly a case where you lower your head and change these pages.
a source to share