disable using "protected override void OnPaint(..." method.

[ramo9941]

Hi,

Is there any way disable using "protected override void OnPaint(..." method
out of the assembly. I create usercontrol and i do not want user adds extra
codes OnPaint method for securtity purpose. And i don't give a permission to
call "CreateGraphics()".

Thanks your responses.

 

[Peter Morris]

protected override sealed void OnPaint..........
{
}

Add the word "sealed" after "override"

 

[ramo9941]

i had used your advice but it has alreay used onpaint outside of the
assembly. I can add "private void graph2D1_Paint(object sender,
PaintEventArgs e)" method from properties->events->paint but ı don't this
event calling.

 

[Jon Skeet [C# MVP]]

i had used your advice but it has alreay used onpaint outside of the
assembly. I can add "private void graph2D1_Paint(object sender,
PaintEventArgs e)" method from properties->events->paint but ? don't this
event calling.

That's adding an event handler for the Paint event, which isn't the
same as overriding the OnPaint method. And no, you can't prevent that.

 

[ramo9941]

ok,
if user adds under codes to "graph2D1_Paint" method:
base.OnPaint(e);
MessageBox.Show("1");
Has any protection mechanism this state?

And same as above state protect to not caling "CreateGraphics()" method
outside of the assembly.

thanks yor replies.

 

[Jon Skeet [C# MVP]]

if user adds under codes to "graph2D1_Paint" method:
base.OnPaint(e);
MessageBox.Show("1");
Has any protection mechanism this state?

No. You can't stop them from calling methods they're normally allowed
to call. That violates object oriented principles. If you don't want
users to be calling certain methods, you shouldn't be deriving from a
class which exposes those methods.

 

[Peter Morris]

i had used your advice but it has alreay used onpaint outside of the

assembly.

Then you shouldn't try to seal it.

 

[Ben Voigt [C++ MVP]]

No. You can't stop them from calling methods they're normally allowed
to call. That violates object oriented principles. If you don't want
users to be calling certain methods, you shouldn't be deriving from a
class which exposes those methods.

As in:

Instead of inheriting, make the object you want to limit access to a private
member (or even a private nested class derived from the base class). Then
you can call any methods on it you want, and intercept any calls your user
makes, because they are not called on the protected object but rather on
your class.