Re: [IronPython] FW: Returning inherited classes to .NET

2008-02-24 Thread Curt Hagenlocher
Using an interface instead of a base class would give you the same > > > > results. > > > > On Thu, Feb 21, 2008 at 9:44 PM, Howland-Rose, Kyle < > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > It runs fine from the command line but then it does not do much

[IronPython] FW: Returning inherited classes to .NET

2008-02-24 Thread Howland-Rose, Kyle
8 4:29 PM To: Discussion of IronPython Subject: Re: [IronPython] FW: returning inherited classes to .NET My apologies; I wasn't reading th

Re: [IronPython] FW: returning inherited classes to .NET

2008-02-21 Thread Curt Hagenlocher
My apologies; I wasn't reading the code correctly. That's probably a sign that I should be going to bed. :) Have you tried simplifying your version just a little bit by running it directly rather than through ASP.NET ? On Thu, Feb 21, 2008 at 8:43 PM, Howland-Rose, Kyle < [EMAI

[IronPython] FW: returning inherited classes to .NET

2008-02-21 Thread Howland-Rose, Kyle
Hi Curt, Thanks for replying. When I view the link I see the following: The .NET code creates the "Test" class and then runs the python code which imports the "Test" class a subclasses it to create python class "X". Class "X" is then called and cast to type "Test" and assigned to the value o