Comments by Michael Ulmann (Top 4 by date)

It's very difficult to judge whether shared/static is what you really need in your circumstances. I'd have to know much more about your project and what you are actually trying to achieve.
In general terms most of the time when designing a software following OO principles information wouldn't make much use of static but have the lifetime of an instance.

If you don't want to look into all this I suggest you make it static but not shared in VB and then use the static accessor in C# as I pointed out in my last suggestion.

Just bear in mind that best practise would be to check for null before using the interface casted object.

Hehe, no worries, happens to all of us every now and then... ;)