How can an auto-implemented property having different access levels be described by an interface?

Question

This class property is what I'm trying to refactor into an interface.

public class Stuff : IStuff {
    public int Number {
        get;
        protected internal set;
    }
}

Visual Studio 2008 refactoring tools extract the following interface

// Visual Studio 2008's attempt is:
public interface IStuff {
    int Number { get; }
}

The C# compiler complains with the error:

'Stuff.Number.set' adds an accessor not found in interface member 'IStuff.DataOperations'

(This is one of the few circumstances I have run into where Visual Studio generates code that causes an improper compile situation.)

Is there a direct solution to extract this one property into an interface without making distinct set and get members/methods on the class?

I see the error when you add the `IStuff` prefix to the `Number` property name.... — CSharpAtl, Dec 09 '09 at 19:13

score 2 · Accepted Answer · answered Dec 09 '09 at 19:11

2

I tested with the following:

class bla : Ibla {
    public int Blargh { get; protected internal set; }
}

interface Ibla {
    int Blargh { get; }
}

and it works just fine. Did you implement the interface correctly?

answered Dec 09 '09 at 19:11

Webleeuw

1

Correct - thank you. I think it was a side-effect of having other compile errors in my code. – John K Dec 09 '09 at 19:20

1 Answers1