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.
I’m working on an interface named IService.
This interface replaces exist one and the application need to refer it as “Service” and not “IService” (I cannot change the application code)
I do not want to break the .Net naming conventions.
Is there a way to add attributes to interface do one defines it reference name?
If you really need keep the name Service for this interface, then you should just call it Service, and make sure its XML comment explains why you omitted the I.
Naming conventions are just that: conventions. As long as you make the reason for deviation clear, you don’t need to follow them all the time.