S
Support
Hello:
I am deploying a new web site that will have over 100 pages.
In the ASP world, I would create templtes - include files, etc... to easily
"manage" the site.
In asp.net 2.0 I want to create a web control but apparently I have to
"create" a web site first.
Concern #1: is VS an appropriate interface to manage 100+ web pages site
conversely
Concern #2: when asp.net 3.0 comes there might be fundamental structural
issues the 3.0 does not like.
Question: should I "break-up" my site into smaller "web sites" ?
I have been a web developer for over 10 years with a lot of ASP experience
and I am encountering this new DOTNET paradigm with discomfort.
For example, I wanted to have a javascript enabled button that would let my
users rate the page they are on. in ASP I would have used <%=
Request.ServerVariables(PATH_INFO) %> as a parameter passed as a querystring
for the survey window... simple! and effective! Now I have to build a
control and have a placeholder, etc....
It's Monday !;-(
Thanks
T
I am deploying a new web site that will have over 100 pages.
In the ASP world, I would create templtes - include files, etc... to easily
"manage" the site.
In asp.net 2.0 I want to create a web control but apparently I have to
"create" a web site first.
Concern #1: is VS an appropriate interface to manage 100+ web pages site
conversely
Concern #2: when asp.net 3.0 comes there might be fundamental structural
issues the 3.0 does not like.
Question: should I "break-up" my site into smaller "web sites" ?
I have been a web developer for over 10 years with a lot of ASP experience
and I am encountering this new DOTNET paradigm with discomfort.
For example, I wanted to have a javascript enabled button that would let my
users rate the page they are on. in ASP I would have used <%=
Request.ServerVariables(PATH_INFO) %> as a parameter passed as a querystring
for the survey window... simple! and effective! Now I have to build a
control and have a placeholder, etc....
It's Monday !;-(
Thanks
T