The OnInit is useful. If it isn't called, then themes and stylesheets
generated in code or through ASP.NET control markup will not be applied.

Signature
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
> The OnInit is useful. If it isn't called, then themes and stylesheets
> generated in code or through ASP.NET control markup will not be applied.
But surely overriding OnInit to just call base.OnInit isn't useful is
it? How can that change anything?

Signature
Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
World class .NET training in the UK: http://iterativetraining.co.uk
Nicholas Paldino [.NET/C# MVP] - 29 Feb 2008 17:26 GMT
I thought you were referring to just the call to OnInit in the override.
The assumption was that there was some other code after the call to OnInit.
If that's all there is in the method definition, then yes, it's pretty
pointless.

Signature
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
>> The OnInit is useful. If it isn't called, then themes and
>> stylesheets
>> generated in code or through ASP.NET control markup will not be applied.
>
> But surely overriding OnInit to just call base.OnInit isn't useful is
> it? How can that change anything?