Hi, I'm wondering if I made a large architectural screwup.  I wanted to use
new features in VS2008 including LINQ in my web service and have targeted the
3.5 framework with the web service.  However, my Windows Forms client targets
the 2.0 framework as I don't want my clients to have to download 3.5

All this works nicely in development but trying to deploy to a staging env I
experience problems.  I've deployed the web service sucessfully to IIS on my
local machine and can browse to the service definition using the address
below OK.

My app.config file contains the reference:
<client>
        <endpoint address="http://rapservice/rap/RapService.asmx"
           binding="basicHttpBinding" bindingConfiguration="RapService1Soap1"
           contract="RapService1.FireService1Soap" name="RapService1Soap1" />
     </client>

I get an error saying 'could not find default endpoint' which I can't seem
to resolve.  It worked in dev and so I did assume 2.0 -> 3.5 was not an
issue, but I'm grasping at straws now having tried everything else and also
seen VS2008 exibit other strange behaviour in the process.. including it
automatically adding TWO <endpoint> addresses (only diff is upper/lower case
address  e.g. RAPSERVICE/rapservice) when I add the service reference.

any ideas?

regards
ewat