Yeah, I wrote a codedom library for ironpython, and had it working with asp.net and everything only to realized that the dll that IP compiles is almost useless for asp.net in the current form.
--Stefan _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith J. Farmer Sent: Thursday, December 08, 2005 2:10 PM To: Discussion of IronPython Subject: Re: [IronPython] NUnit with IronPython Having stable names would be useful outside of unit testing, though, and more attractive in the long run. _____ From: [EMAIL PROTECTED] on behalf of Aidan Downes Sent: Thu 12/8/2005 11:56 AM To: Discussion of IronPython Subject: Re: [IronPython] NUnit with IronPython Doesn't python have its own nunit variant? Pyunit I think. Probably easier to port that over to ironpython. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith J. Farmer Sent: Thursday, December 08, 2005 11:06 AM To: Discussion of IronPython Subject: Re: [IronPython] NUnit with IronPython Assuming IP is going for the .NET producer route, what's the tact for exposing CLR classes with CLR methods? EG, would there be a 'fixed' (as in 'non-dynamic') form of method and field which won't mangle the name, allowing it to be exposed?
<<attachment: winmail.dat>>
_______________________________________________ users mailing list users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
