Recent content by KDavie

How are you loading the controls? Are you using Page.LoadControl?

When working with dynamically generated controls, you are responsible for recreating the controls in each post-back, this includes wiring up your events. Make sure you are re-subscribing to the event on each post-back.

From MSDN..... (Although text is reads VS 2005, applies to 2003 too) full article available at http://support.microsoft.com/kb/318041 ..... Set up remote debugging To use remote debugging, you must add the appropriate user to the Debugger Users group on the remote computer. To do this, follow...

ok... sounds like there is an issue with the web method itself.... What is the web-method doing? Do you have any error handling?

What happens if you browse the web-service from your server and try to invoke a web-method?

Can you post the contents of your app config and the constructor from reference.vb?

Look at the constructor in the proxy... Make sure it is retrieving the correct key from the config file.

Ok... I just double-checked... You should have a Reference.vb file... this is your proxy... you can either view this file in Windows explorer or you can use the show all files option in solution explorer. To view through Windows Explorer: Navigate to your website folder & open the Web...

wsdl.exe is used to generate a proxy for the web service outside of Visual Studio... I was just curious if you used it or just added the web-reference in the VS IDE. It's been a while since I've written a web-service in VB, I thought there was still a reference.vb file but maybe its named...

How did you create the web-reference in your project? Did you add it through visual studio or did you use wsdl.exe?

There is a reference.cs file... Either click the "Show All" button in your solution explorer or navigate to it on your file system.... it will be in your web-reference folder.

k... open the proxy (reference.cs) and make sure that it is retrieving the dynamic URL from the config file. Also, make sure the value (url) in the config file is correct and does in fact point to your deployed instance. If all else fails, delete the web reference and create a new one, this...

The URL behavior property of the web-reference

Check your proxy... It may be pointing to localhost instead of the correct location... did you set it up as dynamic?

Are you able to browse the WSDL on the server?