I currently have a personal website in classic ASP. It is very modular
and relies heavily on subroutines. In particular, I have subroutines
for common design-type scenarios; for instance, I have a subroutine
called Spacer(width, height) that takes height & width attributes and
writes a spacer image; I have another one that takes page-specific
info, like keywords, and concatenates into a more global META
tag-writing subroutine. I also store static design-oriented HTML in
includes.
I'm looking for advice on how to re-architect this website in .NET. I
understand that controls are meant to replace includes, but most of
the examples that I've seen are one-shot page-embedded examples and
not modular, site-wide-type examples.
What I'm looking for is a good explanation of how to re-structure an
existing content-driven ASP website. For instance, should my static
HTML includes go into .ascx files? What about some of the
design-related subroutines? Would they go into .ascx files or class
files?
I have an overall sense of how .NET works and the ways in which it's
different from ASP, but I want to get a better sense of how one should
approach converting a simple, largely-content-driven website from ASP,
as most of the .NET documentation that I've found is aimed at
large-scale websites or forms-heavy websites.
Any advice would be appreciated.
