Seems like a lot of work for simple call to a database. I know I could use classic ASP but I need to learn .NET :)<BR><BR>Thanks for the note about compiling. I have to compile the project or the .aspx page?<BR>
hey are u asking how to deploy the code on the web server or how to call the database in the aspx page. <BR>Well for deploying, yes you need to compile the whole project and then copy it over to the web server.<BR>But if you are testing it locally you can use the build and browse option when you right click on the page in the explorer<BR><BR>HTH
So I just realized that I cannot do what I hope to do. I want to be able to take my existing .asp page complete with Header, Navigation, and Footer #include files (which use classic ASP code) but put .NET content in the body (white space if you will) section.<BR><BR>This is not possible is it?<BR><BR>ALL the Classic ASP content in the #include files will have to get redesigned before using the .NET architecture?<BR><BR>Which would mean that 600 pages will have to get their extension changed from .asp to .aspx?<BR><BR>This is NOT good for search engines or PPC services that clients will undoubtedly be using!!!<BR><BR>So in essence YOU CANNOT redesign sites using .NET, you have to create all new content unless you elect to lose all search engine / PPC settings??
First of all if you are trying to run both asp and aspx pages on the same server then YES it is posible. But I think you want to convert all the pages from asp to aspx and run your existing asp site as aspx site. Now in that case definitely you have to change all the pages from asp to aspx.<BR>As for the #include files, well in .Net you can create a class and all the pages can inherit from that class which I think solves the problem<BR><BR>HTH
>ALL the Classic ASP content in the #include files will have to <BR>>get redesigned before using the .NET architecture?<BR><BR>No. Run them side by side with the aspx pages...And aspx pages can use includes too. It's not preferred...But you can. You really should turn the includes into user controls for the aspx pages if it's feasible.<BR><BR>For your first question....Only the .aspx pages themselves, and the compiled dll need to be uploaded. The resx and vb files do not.