Given :
interface IBanana {//code ommited}
class Banana : IBanana {//code omitted}
ListIBanana banans;
ListIBanana ibanans = banans as ListIBanana;
ibananas == null ? why?
Regards
Arjang
Check out http://www.careerhub.com.au/
_
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Anthony
Sent: Friday, 4 June 2010 12:10 PM
To: 'ozDotNet'
Subject: [OT]Junior Designer/dotnet person required
Where can i post a job requirement for
Cheers Arjang.
This seems to be the best way to understand the type variance rules and why
they used the terms in/out in the implementation.
If all uses of the generic type parameter are in return (or out) positions
then you can get out variance. If all uses are in incoming positions (i.e.
Haha. I didn't even read it properly. Pattern Matching FTW!
On Fri, Jun 4, 2010 at 3:08 PM, Mark Hurd markeh...@gmail.com wrote:
I assume the OP has a typo and he's trying to cast to IList, and all
your answers are assuming that!
The 'exact' code he's posted does not return null.
--
Folks, I added a Customer Information dialog to my VS2008 installer project.
I expected the serial number the user enters to be present in the Context
collection that my Custom Action could validate, but it's not there. All of
the data entered in other dialogs is in the Context collection.
Has
