D
D. Shane Fowlkes
I posted this on another forum, and as I feared, the response(s) were too
complex and sophisticated. I certainly don't mind learning new methods, in
fact, that's why I asked, but I was hoping to emphasize that needed to take
small steps. The responses I received talked about Public Classes and DLLs
and such. =(
I'm tinkering in ASP.NET 2 (VB) and have been tinkering with VWD for about a
couple of weeks. I've written a few app pages that use a simple code-behind
method where I place all my subs and functions on a .vb page and just
"include" on the needed page like so (spaces added intentionally):
< % @ Page language="VB" CodeFile="CodeFiles / default_aspx . vb"
Inherits="LogInClass" % >
This seems to work well. I've managed to place my MSSQL connection string
in my web.config file to centralize this connect string. But what would you
recommend as far as centralizing all "global" values and possibly subs and
functions?
I have a few subs and functions that I can use on many different pages so it
would make sense to place them in one place. Please keep in mind that I'm
new to .NET (but not ASP programming) and VWD. Up until this point, I've
coded all my asp inline by hand and using Dreamweaver to manage / build
sites. I'm looking for a effectice but simple way to do this.
Would it be as easy as creating another .vb file and "including" it in the
required pages too? Or would I create a ascx file and use @Register it to
"include" it in these .vb files?
Thanks!
complex and sophisticated. I certainly don't mind learning new methods, in
fact, that's why I asked, but I was hoping to emphasize that needed to take
small steps. The responses I received talked about Public Classes and DLLs
and such. =(
I'm tinkering in ASP.NET 2 (VB) and have been tinkering with VWD for about a
couple of weeks. I've written a few app pages that use a simple code-behind
method where I place all my subs and functions on a .vb page and just
"include" on the needed page like so (spaces added intentionally):
< % @ Page language="VB" CodeFile="CodeFiles / default_aspx . vb"
Inherits="LogInClass" % >
This seems to work well. I've managed to place my MSSQL connection string
in my web.config file to centralize this connect string. But what would you
recommend as far as centralizing all "global" values and possibly subs and
functions?
I have a few subs and functions that I can use on many different pages so it
would make sense to place them in one place. Please keep in mind that I'm
new to .NET (but not ASP programming) and VWD. Up until this point, I've
coded all my asp inline by hand and using Dreamweaver to manage / build
sites. I'm looking for a effectice but simple way to do this.
Would it be as easy as creating another .vb file and "including" it in the
required pages too? Or would I create a ascx file and use @Register it to
"include" it in these .vb files?
Thanks!