Hi Greg,

Boy, do I bother you alot...

I have a service that implements two interfaces, IServiceA and IServiceB. They are complementatry, but different, so the scheme makes sense.

I would like to expose them on the endpoints:

http://myServer:20000/MyService/ServiceA
http://myServer:20000/MyService/ServiceB

However, when I add the first endpoint for wsHttp, you must use a base address, so the first endpoint is correct, but when I add the second, since it cannot be a base address, I am left with:

http://myServer:20000/MyService/ServiceA
http://myServer:20000/MyService/ServiceA/ServiceB

Is there a way around this I am missing?

***Edit***
I've decided this probably doesn't matter anyhow...obviously creating a service client on either of the endpoints in the scheme results in both interfaces.

Thanks,
Darren

since addresses are always relative in IIS-hosted sites, wrt to the virtual directory; config services always uses a base address + relative address scheme; so you must go with this. The first address for a network scheme is always the base address, every address after that becomes relative to this base.

-Greg

---

Greg Leake, Microsoft

since addresses are always relative in IIS-hosted sites, wrt to the virtual directory; config services always uses a base address + relative address scheme; so you must go with this. The first address for a network scheme is always the base address, every address after that becomes relative to this base.

-Greg

---

Greg Leake, Microsoft

Cool. I did things this way becuase I wanted to deal with self-hosted and IIS-hosted services in a consistent way. Underneath, there are several differences between hosting WCF in IIS and self-hosting, however.

-Greg

---

Greg Leake, Microsoft