D
DBxGlock
Howdy folks,
Recently we copied a .NET 1.1 aspx page and dll to a production server.
The page had a web reference to a service that we have running on the
production server, as well as another version running on the test
server. Everything ran fine in production until the test server went
down, and we noticed that the page that was put on the production
machine had its web reference pointing to the web service on the test
machine. Is there a way to examine a DLL for an aspx page to determine
where it's going to look for its web reference?
Thanks,
Dan
Recently we copied a .NET 1.1 aspx page and dll to a production server.
The page had a web reference to a service that we have running on the
production server, as well as another version running on the test
server. Everything ran fine in production until the test server went
down, and we noticed that the page that was put on the production
machine had its web reference pointing to the web service on the test
machine. Is there a way to examine a DLL for an aspx page to determine
where it's going to look for its web reference?
Thanks,
Dan