Hi All,
Just spent the last few hours working through a few issues, getting stuff up and running on the abovementioned configuration. I thought it would be worth sharing a couple of basic things I learnt, so others don't waste the same amount of time I have ...
Firstly, installing VS.NET 2008 Team Suite, even with all the SDK options selected, will NOT give you enough tools to generate the web service client stuff correctly. The install will provide you with the WSDL.exe tool, but it doesn't give you the DISCO.exe tool. I fixed this issue by using my VS.NET 2005 Team System installation disk, and deselecting everything EXCEPT the SDK stuff, however, I expect you can just install the .NET Framework SDK 2.0 (350-odd MB), and the tools you need will be installed that way as well.
The second issue I ran into was that the Web Services project isn't given enough rights when it's created. This creates all kinds of problems, because (1) you can't view the web services with the browser, and (2) you can't regenerate the web service proxies in the Web References of the Web Service Client project. This one threw a curve ball at me, because the actual error I was getting stated that there were errors in my web.config file. Not so! You need to grant "Read & Execute", "List Folder Contents" and "Read" rights to the "Users" and "IIS_IUSRS" groups, in the Security settings of your WebServices folder (ie Properties / Security / Edit / Add).
Then remove your Web Service Client project from the Solution. Rebuild the solution. Add the Web Service Client project back to the solution. Go to the WsProxy node in the Web Service Client project, right click and Update Web References. The Web References will update, and there will be a couple of stray files left over (make sure you select Show All Files in the Solution Explorer) that you can delete.
After that, everything should build and run correctly! At least, until that point ... :-D
T