1

I'm struggling to come up with the correct naming convention for SVC files (or a group of SVC files). I always call them just that.

IMyService.cs goes in MyProject.Contracts dll assembly

MyService.cs goes in MyProject.Services dll assembly

MyService.svc goes in MyProject.???? web application assembly

What's the correct naming convention here. I'm having a complete monday-brain about it and can't get the term facade out of my head which I know is wrong.

Eoin Campbell
  • 43,500
  • 17
  • 101
  • 157

3 Answers3

4

Technically, an svc file represents a service host (hence the @ServiceHost directive it contains).

So, maybe MyProject.Hosting or MyProject.ServiceHosts would be appropriate.

Frédéric Hamidi
  • 258,201
  • 41
  • 486
  • 479
2

I would use .Web. It's a web application.

Or possiby, MyProject.Services.Web if the .Web suffix is already gone?

Andras Zoltan
  • 41,961
  • 13
  • 104
  • 160
  • I can't... further down my stack I have a .Web Project which is the front end... this is a seperate web project which gets installed on a different server dedicated to backend services. Maybe .WebServices is good enough. – Eoin Campbell Mar 06 '12 at 12:25
  • @EoinCampbell - yeah `.WebServices` is nice - or how about `.Services.Web`? (Have updated with this suggestion) – Andras Zoltan Mar 06 '12 at 12:32
1

We've used .API to differentiate it from a regular website front end.

Steve Wilkes
  • 7,085
  • 3
  • 29
  • 32