Rafael is correct. I would add that if you're planning on doing something immediately that the C# compiler is in a much more usable state. We're currently working on the Basic compiler and the VisualBasic.dll, but progress (at least on my side) has been slow of late.
Chris J. Breisch, MCSD, MCDBA -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of A Rafael D Teixeira Sent: Wednesday, July 31, 2002 10:11 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Mono-list] Cross platform development: VB.NET or C# >From: "William Wise" <[EMAIL PROTECTED]> > >My question for the list is: What can I do to insure that the migration >will be as smooth as possible? Should I use VB.NET or C# as the >development >language? Any other factors that I should consider or libraries I should >avoid using? Language is your choice: we are working on both compilers, and supporting runtime libraries. Just avoid any Win32 API calls, be carefull with third party Win Forms Controls and/or Libraries that don�t say they are Mono Compatible, and track development of substitutes for bigger roadblocks like COM+ interop, MSMQ, ADSI (namely System.EnterpriseServices, System.Messaging, etc...) Rafael Teixeira Brazilian Polymath _________________________________________________________________ Join the world�s largest e-mail service with MSN Hotmail. http://www.hotmail.com _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
