Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

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.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 679075
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T01:13:11+00:00 2026-05-14T01:13:11+00:00

Interfaces, as defined by MSDN contain only the signatures of methods, delegates or events.

  • 0

Interfaces, as defined by MSDN “contain only the signatures of methods, delegates or events.” However, since properties are no more than syntactic sugar for a get and set method, they are also allowed in interfaces. My question is – is there any situation where defining properties in an interface is appropriate or should we stick to the scenarios described by MSDN?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T01:13:12+00:00Added an answer on May 14, 2026 at 1:13 am

    I think properties are perfectly acceptable in interfaces.

    As you said, they really are a get, set, or get and set method. Many interfaces in the Framework define properties, such as IAsyncResult and IWebProxy.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

edit4: wikified, since this seems to have morphed more into a discussion than a
I have defined an interface in C++, i.e. a class containing only pure virtual
Interfaces allow you to create code that defines the methods of classes that implement
Q1 Why do new classes from .NET implement interfaces only partially? Q2 Shall I
I have the following interfaces defined: public interface IAudit { DateTime DateCreated { get;
I have a marker interface defined as public interface IExtender<T> { } I have
I have an NSWindow that I defined in interface builder. I want to make
I have an interface that I have defined in C++ which now needs to
I just ran into the user-defined conversions to or from an interface are not
I have a interface that defines some methods with attributes. These attributes need to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.