T
Tom Wilson
I'm in a pickle.
Maybe you guys can shed some light.
I am setting up a web site that uses a ADO and SQL server. My first site
went well, and works wonderfully. So I use the same classes and modules I
developed to build a second site. I'm developing and testing on a Windows XP
machine, then copying the files to a Win2k Server. It has dotNet 1.1
installed.
Here's the weird thing. I can't use the database on the second site. Any
time I try to access a field in the recordset, I get really strange errors
(and they're not consistent. The errors change with NO changes in the code).
I've got it narrowed down to this: The only way I was able to get site 1 to
function was to copy adodb.dll into the /bin directory (the same directory
as the site's compiled DLL). When I uploaded and set up site 2, I did the
same thing. However, I can't access the database. If I restart the web
server, I can use the DB on site 2, but then site 1 doesn't work.
My theory is that once a site loads the adodb.dll assembly, everybody else
tries to use that loaded copy, but they can't because it's in a different
web site's /bin directory and .Net's security is tighter than Reagan Airport
on September 12. Apparently I need to install ADODB.DLL in a common location
that both sites can access. But I've tried dropping it everywhere I can
think of: winnt\system, the Microsoft.Net directory under WINNT, different
directories under Microsoft.Net.... the only solution was to install Visual
Basic.Net on my web server. However, I can't do this on a production server,
and I definitely can't buy and install VB on every single server that I
deploy web projects on.
So how do I install and use ADODB.DLL without having to install VB? Is there
some trick that I can use to install a shared copy of ADODB.DLL that
everybody can "play nice" with?
Maybe you guys can shed some light.
I am setting up a web site that uses a ADO and SQL server. My first site
went well, and works wonderfully. So I use the same classes and modules I
developed to build a second site. I'm developing and testing on a Windows XP
machine, then copying the files to a Win2k Server. It has dotNet 1.1
installed.
Here's the weird thing. I can't use the database on the second site. Any
time I try to access a field in the recordset, I get really strange errors
(and they're not consistent. The errors change with NO changes in the code).
I've got it narrowed down to this: The only way I was able to get site 1 to
function was to copy adodb.dll into the /bin directory (the same directory
as the site's compiled DLL). When I uploaded and set up site 2, I did the
same thing. However, I can't access the database. If I restart the web
server, I can use the DB on site 2, but then site 1 doesn't work.
My theory is that once a site loads the adodb.dll assembly, everybody else
tries to use that loaded copy, but they can't because it's in a different
web site's /bin directory and .Net's security is tighter than Reagan Airport
on September 12. Apparently I need to install ADODB.DLL in a common location
that both sites can access. But I've tried dropping it everywhere I can
think of: winnt\system, the Microsoft.Net directory under WINNT, different
directories under Microsoft.Net.... the only solution was to install Visual
Basic.Net on my web server. However, I can't do this on a production server,
and I definitely can't buy and install VB on every single server that I
deploy web projects on.
So how do I install and use ADODB.DLL without having to install VB? Is there
some trick that I can use to install a shared copy of ADODB.DLL that
everybody can "play nice" with?