B
Bob Delaney
Many thanks to the three people who responded to yesterday's post with
some helpful suggestions. They asked what I am trying to do. Here is a
synopsis:
I have a web site (www.mississaugawest.com if you want to look at it)
that I wouldn't mind porting to ASP.Net in its next version. I am a Member
of Provincial Parliament in Ontario Canada, and a former MVP in Windows XP,
back when I had time to do the postings.
The ASP classic web site works on a frameset, and uses an Access
database, a lot of client-side Javascript - including the navigation menu,
and some server-side VBScript. It may be old technology, but it does work!
I am impressed with what I have read and seen in my books, in the
tutorials, on MSDN and in the MS seminars I have attended. It seems that the
Master Page is intended to serve as the type of container for a title bar
and a navigation menu that my frameset is. That's what I'd like to use the
Master Page and the linked Content Pages for.
What I am trying to do in the new site, for my 2007 re-election, is use
ASP.Net 2.0 and upgrade the technology, partly for what it actually does,
and partly so that my weekend coding skills do not go completely rusty and
that I learn to use the new technology. See the very early version at
www.mississaugastreetsville.ca.
One can say that if it works, then stick with it, and indeed, I may end
up doing the new site with classic ASP if I can't figure out how to get
ASP.Net started. However, with a bit of time while the Legislature is in
recess, I would like to master the Master Page and ASP.Net 2.0. A lot of my
JavaScript is driven by code in the header, or linked to shared code stored
in my /scripts folder. Assuming that compiled VB.Net code in the code-behind
file can drive a page load event, then perhaps porting some of that
client-side JavaScript to compiled VB, which I assume is (or can be made to
be) client-side driven (if the runat="server" is not used), might do what I
need done, and get me using Visual Studio.Net 2005 as well.
If that makes the situation clearer, and helping a former MVP is up your
alley, then I'd welcome any advice to assist me with a solid web site to
keep this MVP as perhaps the only alumnus of the MVP fraternity to sit in an
elected Legislature. And if you don't think that the knowledge base many of
us have learned researching posting responses isn't absolutely wicked fun
when the bureaucracy tries some bafflegab anticipating that the elected
members are the usual technophobes, then perhaps I have a few amusing
anecdotes in return for assistance. Joyeux Noel!
Bob Delaney
some helpful suggestions. They asked what I am trying to do. Here is a
synopsis:
I have a web site (www.mississaugawest.com if you want to look at it)
that I wouldn't mind porting to ASP.Net in its next version. I am a Member
of Provincial Parliament in Ontario Canada, and a former MVP in Windows XP,
back when I had time to do the postings.
The ASP classic web site works on a frameset, and uses an Access
database, a lot of client-side Javascript - including the navigation menu,
and some server-side VBScript. It may be old technology, but it does work!
I am impressed with what I have read and seen in my books, in the
tutorials, on MSDN and in the MS seminars I have attended. It seems that the
Master Page is intended to serve as the type of container for a title bar
and a navigation menu that my frameset is. That's what I'd like to use the
Master Page and the linked Content Pages for.
What I am trying to do in the new site, for my 2007 re-election, is use
ASP.Net 2.0 and upgrade the technology, partly for what it actually does,
and partly so that my weekend coding skills do not go completely rusty and
that I learn to use the new technology. See the very early version at
www.mississaugastreetsville.ca.
One can say that if it works, then stick with it, and indeed, I may end
up doing the new site with classic ASP if I can't figure out how to get
ASP.Net started. However, with a bit of time while the Legislature is in
recess, I would like to master the Master Page and ASP.Net 2.0. A lot of my
JavaScript is driven by code in the header, or linked to shared code stored
in my /scripts folder. Assuming that compiled VB.Net code in the code-behind
file can drive a page load event, then perhaps porting some of that
client-side JavaScript to compiled VB, which I assume is (or can be made to
be) client-side driven (if the runat="server" is not used), might do what I
need done, and get me using Visual Studio.Net 2005 as well.
If that makes the situation clearer, and helping a former MVP is up your
alley, then I'd welcome any advice to assist me with a solid web site to
keep this MVP as perhaps the only alumnus of the MVP fraternity to sit in an
elected Legislature. And if you don't think that the knowledge base many of
us have learned researching posting responses isn't absolutely wicked fun
when the bureaucracy tries some bafflegab anticipating that the elected
members are the usual technophobes, then perhaps I have a few amusing
anecdotes in return for assistance. Joyeux Noel!
Bob Delaney