Many thanks. Your post is
a keeper.
I've got SQL Server working
now with notes on how I did it
and with some simple text files
with SQL commands to be run
with the Microsoft SQLCMD.EXE
for setting security.
For the connection string,
I found something that is working
and, of course, have it documented,
saved, etc. To define the
tables and columns, I have that also
as just simple text in a file
run with SQLCMD.EXE.
To keep SQL Server installation
problems from ruining my boot main
partition, finally I am good
at using NTBACKUP to get a
clean backup and know how to
restore it. So, before doing
anything like a SQL Server install,
I will use NTBACKUP to save
the main boot partition.
If SQL Server messes up, then,
boom, I will just restore the
boot partition and start over
with the SQL Server install.
The worst time with SQL Server
installs it wasn't clear what
the heck to click on, ended
up with two versions installed
side by side, tried to uninstall
one, and ended up with a sick
SQL Server that wouldn't do
even the simplest things.
Another time I wanted SQL Server
to use a database from
an earlier install, and trying
to do this got SQL Server sick.
Trying to uninstall and reinstall
ruined my boot partition.
But, as soon as I can get the
other work done, I will get
the first server computer
for my "server farm", install
some recent versions of Windows
Server, SQL Server, IIS, etc.
and go live. Then, with
Windows Server, etc., I will
be back into system management
again.
Today I am fixing a bug in
my Web site: I have two
Web pages where they use
server.transfer
to send a user from one to the
other, and I have a fairly
elaborate session state to be
saved in one page and restored
in the next one (instead of
Redis, wrote my own session
state store with just
de/serialization from/to
byte strings of instances of
my session state class and
two collection classes). But
going between the two pages
I must have coded when
half asleep and didn't get
quite right. So fixing that now.
Also putting in lots of documentation
to make it clear just what
is going on.
My wisdom in building a Web
site with ASP.NET: Start with
the class for the session state
you want for your site.
That is, concentrate on this
data, with essentially global
scope. The first crucial work
is just being really clear on
just what the session state data
is to be.
The second most
important thing is to be clear
on just how ViewState works.
ViewState is useful and
can save some coding.
Third, in positioning things
on the Web page, maybe
make good use
of instances of the class
Place Holder.
Fourth, have clearly in mind
all the data that is available
from a post back -- some of that
data can be useful.
Fifth, make good use of the
ability to write data to the
log file.
Last, have
clearly in mind when
routines
Page_Init
Page_Load
the button click routines
Page_Unload
etc. run.
After that, just keep it
all simple and clear for the
user.