N
Nathaniel Sherman
Alright, folks, here's the deal...
I'm working on migrating a classic ASP website to an ASP.NET codebase.
At the heart of the site is a MySQL database.
To make sure an "in-process" program doesn't screw up the live site, I
run a local IIS webserver on my XP Pro (AMD XP 2500+, 512MB DDR RAM)
machine, which resides behind an XP ICS gateway on my LAN. I also have a
MySQL server set up locally for development purposes.
Now, I use essentially the same code for database functionality in
ASP.NET that I'm using in the ASP pages -- thanks to the .NET ADODB
wrapper (Note that I am NOT using ADO.NET per se, but that I have tried
and get the results I'll speak of later) Using said code, connections to
both my local DB server and the DB server which resides on my hosting
provider's servers are initiated quite quickly. The code also works
great in ASP.NET form if compiled and run from the hosting provider's
webserver.
Unfortunately, it takes a good 15-20 seconds to run the
ADODB.Connection.Open() method if I try to run the same ASPX page on my
local webserver. Note that this dramatic pause occurs regardless of
server address/name, and does not seem to be directly related to the
success of the function. And it gets better than that -- if I disable
the server computer's connection to my LAN (and thus, the internet as
well) the connections are lightning quick, as they're apparently
supposed to be.
The only possible explanation I can come up with is that it's DNS
related, somehow... Lookups and reverse-lookups getting snagged
somewhere... Though, one wouldn't think that and DNS-related functions
would have to be used in order to process "localhost" or "127.0.0.1"...
In any case, I've been to the end of the 'net and back again (heh)
multiple times looking for a possible solution to this problem. At this
point, I'd even settle for any evidence that anyone else anywhere is
HAVING this problem... At least then I'd no I'm not just losing my mind.
Considering VS.NET has the ability to build to and debug directly from a
remote server using FrontPage extensions, it wouldn't be the absolute
end of the world if that's the only way I could develop ASP.NET web apps
and services... But it would be nice to have some clue as to what's
going on.
If anyone could shed any light on this issue, I'd be eternally grateful.
Thanks in advance.
I'm working on migrating a classic ASP website to an ASP.NET codebase.
At the heart of the site is a MySQL database.
To make sure an "in-process" program doesn't screw up the live site, I
run a local IIS webserver on my XP Pro (AMD XP 2500+, 512MB DDR RAM)
machine, which resides behind an XP ICS gateway on my LAN. I also have a
MySQL server set up locally for development purposes.
Now, I use essentially the same code for database functionality in
ASP.NET that I'm using in the ASP pages -- thanks to the .NET ADODB
wrapper (Note that I am NOT using ADO.NET per se, but that I have tried
and get the results I'll speak of later) Using said code, connections to
both my local DB server and the DB server which resides on my hosting
provider's servers are initiated quite quickly. The code also works
great in ASP.NET form if compiled and run from the hosting provider's
webserver.
Unfortunately, it takes a good 15-20 seconds to run the
ADODB.Connection.Open() method if I try to run the same ASPX page on my
local webserver. Note that this dramatic pause occurs regardless of
server address/name, and does not seem to be directly related to the
success of the function. And it gets better than that -- if I disable
the server computer's connection to my LAN (and thus, the internet as
well) the connections are lightning quick, as they're apparently
supposed to be.
The only possible explanation I can come up with is that it's DNS
related, somehow... Lookups and reverse-lookups getting snagged
somewhere... Though, one wouldn't think that and DNS-related functions
would have to be used in order to process "localhost" or "127.0.0.1"...
In any case, I've been to the end of the 'net and back again (heh)
multiple times looking for a possible solution to this problem. At this
point, I'd even settle for any evidence that anyone else anywhere is
HAVING this problem... At least then I'd no I'm not just losing my mind.
Considering VS.NET has the ability to build to and debug directly from a
remote server using FrontPage extensions, it wouldn't be the absolute
end of the world if that's the only way I could develop ASP.NET web apps
and services... But it would be nice to have some clue as to what's
going on.
If anyone could shed any light on this issue, I'd be eternally grateful.
Thanks in advance.