StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1278417
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2009-08-14T15:07:14.310
FavoriteCount
0
LastActivityDate
2009-08-14T16:42:01.780
LastEditDate
2009-08-14T16:42:01.780
LastEditorUserId
13302
OwnerUserId
13302
ParentId
1278332
PostTypeId
2
Score
11
ViewCount
0
LastEditorDisplayName
text
Body
OK, so the most important things are: <ul> <li>address</li> <li>binding</li> <li>contract </li> </ul> and then some additional stuff thrown in. 1) Address: Get this from here: <pre><code>WebServiceHost host = new WebServiceHost( typeof(MyService), new Uri("http://localhost:80/")); host.AddServiceEndpoint(typeof(MyService), new WebHttpBinding(), ""); </code></pre> and here: <pre><code>ServiceEndpoint sbEndpoint = host.AddServiceEndpoint( typeof(MyService), new WebHttpRelayBinding(), "http://azureURL"); </code></pre> so you'll need something like: <pre><code><endpoint address="" <endpoint address="http://azureURL" <endpoint address=""http://someURL" </code></pre> in your service. 2) Binding: The first endpoint is a webHttpBinding, the second one uses a custom binding ("MyBinding") - so you have: <pre><code><endpoint address="" binding="webHttpBinding" <endpoint address="http://azureURL" binding="webRelayHttpBinding" <endpoint address=""http://someURL" binding="myBinding" </code></pre> and you'll need to define your custom binding: <pre><code><bindings> <customBinding> <binding name="MyBinding"> .. define the parameters of your binding here </binding> </customBinding> </bindings> </code></pre> or create a <code><extensions></code> section for your binding stored in code in a separate assembly. 3) Contracts I don't clearly see a contract anywhere - you only ever use the typeof(MyService), but usually, this is the concrete service instance, not the service contract which should be an interface (something like <code>IMyService</code>). Why don't you have an explicit service contract? Anyway, if your service implementation is the contract, too, at the same time (not best practice! but possible), then you have your two endpoints like this: <pre><code><endpoint address="" binding="webHttpBinding" contract="MyService" /> <endpoint address="http://azureURL" binding="webHttpRelayBinding" contract="MyService" /> <endpoint address="http://someURL" binding="myBinding" contract="MyService" /> </code></pre> You then need to add a few sprinkles here and there (define the "base address" of the service, give the service a name and so on), and should end up with something like: <pre><code><system.serviceModel> <bindings> <customBinding> <binding name="MyBinding"> .. define the parameters of your binding here </binding> </customBinding> </bindings> <services> <service name="YourNameSpace.MyService"> <host> <baseAddresses> <add baseAddress="http://localhost:80/" /> </baseAddresses> </host> <endpoint address="" binding="webHttpBinding" contract="MyService" /> <endpoint address="http://azureURL" binding="webHttpRelayBinding" contract="MyService" /> <endpoint address="http://someURL" binding="myBinding" contract="MyService" /> </service> </services> </system.serviceModel> </code></pre> Now all you're missing is the behavior defined - I'll leave that as an exercise for the poster :-) Does that help anything? As for references - hmmm..... hard to say.... I guess the usual books ("Learning WCF" by M.L.Bustamante for beginner/intermediate, "Programming WCF" by Juval Lowy for intermediate/advanced) are my best bet, and lots of experience, really. I don't know of any source that explicitly shows and teaches how to convert between settings in code and config - the two books mentioned usually show both ways, and from this, you can figure it out yourself. Marc
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConverting programmatic configuration of WCF service to config file
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmarc_s
UserOwnerUserId
1. USmarc_s
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POConverting programmatic configuration of WCF service to config file
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks for explaining the process of building the configuration file. As you expected, the service implementation is the contract, too. I've chosen this as the contract consists only of two very general function and is not reusable. I've tried first just with the webHttpBinding and commented out the existing programmatic setup. However, it doesn't work. The service isn't accessible when I open http://localhost in my web browser. Do I have to make some other settings for the application in VS? (It's a standard "Console application" at the moment.)
 singulars
 PostPostId
 PO
 UserUserId
 USEtan
2. COWell, one problem you have is: for the webHttp binding, you need the WebServiceHost - for the other bindings, you need the straight ServiceHost - so you probably won't be able to host all endpoints in a single (Web)ServiceHost
 singulars
 PostPostId
 PO
 UserUserId
 USmarc_s

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.