Hi, Just wondering how much pain is involved in taking an existing website created with Dreamweaver (mostly just plain HTML + some javascript) then converting each page to ASP.NET with Code-Behind for each page? The website is a mockup in plain HTML so there is no database hooked up yet. I'm assuming plain HTML elements like input text boxes can easily be replaced using the Visual Studio Designer. Thanks for any input, Frank
> Just wondering how much pain is involved in taking an existing website > created with Dreamweaver (mostly just plain HTML + some javascript) then > converting each page to ASP.NET with Code-Behind for each page? If it's just HTML, there there is no code to put into codebehind. If it's just HTML, there really is no reason to 'convert' it to anything else, as it's just HTML. > The website is a mockup in plain HTML so there is no database hooked up > yet. > I'm assuming plain HTML elements like input text boxes can easily be > replaced using the Visual Studio Designer. What, ultimately, are you trying to accomplish with this 'conversion'? -Darrel
