What are the best practices for naming WCF endpoints and methods? What are the conventions you usually follow?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What are the best practices for naming WCF endpoints and methods? What are the conventions you usually follow?
I’m not aware of any specific naming conventions here – just use something “appropriate”, define a standard, and stick to it 🙂
If you’re dealing with SOAP web services, those are typically more geared towards functions / methods – e.g. your methods would be something like
GetCustomerorUpdateCustomerOrderor stuff like that. Try to come up with a consistent naming – don’t useGet....once,Fetch....the other time, andLoad....the next time. Same for saving: don’t useSave....,Store..orPut...– settle on one and stick to it.If you’re more into the REST style of WCF – then you’re dealing more with resources, e.g. you would have
CustomerandOrderandInventoryas resources in your URL, and then use the basic HTTP verbs (GET, PUT, POST, DELETE) to handle the basic CRUD operations.