Running on seperated server

Aug 27, 2007 at 7:32 PM
Hi!

I really love your project and I think it really rocks, but enough for the compliments ;)

I'm having a bit of problem setting the server to work on a seperate server. I have set up the database to the other server and I have also got the Web Service running there nicely. My problem is the client. Even if I set the web.config to refer to the http://mysite.mydomain.com/Services location the program always tries to connect to the default localhost address and ends up crashing for this cause.

I tried this even on the example project by changing the web.config to reference to my seperate server. Everytime I run the project it also starts the localhost web service and if I quit that development server the program will crash. To me it seems like the system isn't actually reading the information that is within the web.config file (or app.config). Please guide me to the right direction, I'm totally lost here.

BR.

Gabfine
Coordinator
Sep 7, 2007 at 4:35 AM
Thanks for the compliments!

I apologize for taking so long to respond!

Well you're gonna laugh at this, but the problem you're running into is a missing forward slash at the end of your Url. I need to make it a little smarter, but for now the slash is requires.

So make your webserviceurl this instead:
http://mysite.mydomain.com/Services/

To see more info about this, checkout the contructor in any of the web service consumer classes (reference.cs). You'll see where I override the Url property.

On a side note, this is a regular web application, so you should be able to set it up with a database on one service, the website on another (or pool of others) and the clients, obviously, on their own machines.

Thanks! Good luck!