You may find some issues with that since it's a CTP (pre-beta) from 2006, so some supported syntax in there may have changed for final release, but can't say for certain.
Teravus is correct in that VS2008 is available for free (http://www.microsoft.com/express/vcsharp/). Installing C# 2008 Express you also get SQL Server 2008 Express installed, so you have some options for using that out of the box too. C# Express should be able to handle most basic development tasks - I guess it just depends on how nice you want to be to 2005 Pro or higher owners going forward as to whether to stay in 2.0 land or move on. From: [email protected] [mailto:[email protected]] On Behalf Of Stefan Andersson Sent: 26 March 2009 07:45 To: [email protected] Subject: Re: [Opensim-dev] C# 3.0 vs .Net 2 Could anybody actually using VS 2005 comment on whether installing the Orcas CTP would solve this? http://www.microsoft.com/downloads/details.aspx?FamilyId=1E902C21-340C-4 D13-9F04-70EB5E3DCEEA&displaylang=en This is the community preview of the C# 3 extensions, made available as an extension to VS 2005. Best regards, Stefan Andersson Tribal Media AB > Date: Thu, 26 Mar 2009 01:27:42 -0400 > From: [email protected] > To: [email protected] > Subject: Re: [Opensim-dev] C# 3.0 vs .Net 2 > > Our issue here isn't mono support :) Mono has 3.0 support since > 1.9.1. It's our support of Visual Studio 2005 as a build tool. > > Visual Studio 2005 is the tool that doesn't understand code in C# 3.0 :). > > Visual Studio 2008 will generate a 2.0 assembly from 3.0 code. > Visual Studio 2005 will fail to build. > > As far as I really know.. the only reason to support Visual Studio > 2005 right now is for people who have Visual Studio 2005 Standard, > Pro, or Team licenses. Visual Studio 2008 Express is freely > downloadable and available and Mono is quite happy with 3.0 syntax > > Sincerely > > Teravus > > On 3/26/09, Frisby, Adam <[email protected]> wrote: > > > > > > > > If we consider a shift to .NET 3, I'd like to also propose utilizing the new > > Socket members that .NET 3 introduced - there is some in there for high > > performance ASync socketing which perform significantly better than previous > > ones in the kinds of situations we employ. > > > > > > > > (As long as Mono 2.0.2 has those implemented of course - but it shouldn't be > > hard for the, they could at least just make them a splint to the old > > methods) > > > > > > > > Adam > > > > > > > > > > > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > > Ruud Lathrop > > Sent: Wednesday, 25 March 2009 11:34 AM > > To: [email protected] > > Subject: Re: [Opensim-dev] C# 3.0 vs .Net 2 > > > > > > > > > > Visual Studio 2005 is using .NET 2.0/C# 2, only with some extending can you > > use some .NET 3/C# 3 features (WCF is the best known). > > > > It seems that Visual Studio 2008 is doing some tricks for you when you have > > a .NET 2.0 project, but use .NET 3/3.5 syntax. Like this: > > > > public string Test { get; set; } > > > > Just works in a .NET 2.0 project, same with lambda, while it is .NET 3/ C# 3 > > specs > > > > Ruud > > > > > > > > On Wed, Mar 25, 2009 at 3:57 PM, Teravus Ovares <[email protected]> wrote: > > > > The problem with Lamda Expressions isn't compiling to IL 2.0.. it's > > compiling in Visual Studio 2005. Visual Studio 2005 will not compile > > Lamda Expressions at all. > > > > Regards > > > > Teravus > > > > > > > > On 3/25/09, Sean Dague <[email protected]> wrote: > > > Stefan Andersson wrote: > > > > Yo. > > > >=20 > > > > =20 > > > >=20 > > > > Feeling a bit stupid here, but just realized that many C# 3.0 features = > > > (lambda expressions and inferred types, for example) compiles just fine t= > > > o the .Net 2 IL, so in practise, it can be used if the installed csc supp= > > > orts it. > > > >=20 > > > > =20 > > > >=20 > > > > What I'm saying is that we can probably start using some C# 3.0 feature= > > > s already even on mono (I guess) without moving from .Net 2.0. Question i= > > > s, what features? > > > >=20 > > > >=20 > > > > Could any mono person have a look at what C# 3.0 constructs are actuall= > > > y backwards compatible with .Net 2.0 on mono? > > > > > > One approach would be to make a new unit test that used some of those > > > features, then it would be easy for people to test with their > > > environment. I suspect mono 1.9.1 is still going to have issues, and we > > > haven't committed to dumping it yet (as that's what is shipping in the > > > latest stable release of Ubuntu, which a lot of people are using). > > > > > > The new Ubuntu release comes out in April with Mono 2.0.2, so we can > > > leave 1.9.1 behind in the near future. > > > > > > -Sean > > > > > > --=20 > > > Sean Dague / Neas Bade > > > [email protected] > > > http://dague.net > > > > > > > > > > > > > > _______________________________________________ > > > Opensim-dev mailing list > > > [email protected] > > > https://lists.berlios.de/mailman/listinfo/opensim-dev > > > > > > > > > > > _______________________________________________ > > Opensim-dev mailing list > > [email protected] > > https://lists.berlios.de/mailman/listinfo/opensim-dev > > > > > > _______________________________________________ > > Opensim-dev mailing list > > [email protected] > > https://lists.berlios.de/mailman/listinfo/opensim-dev > > > > > _______________________________________________ > Opensim-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-dev No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.238 / Virus Database: 270.11.22/2015 - Release Date: 03/24/09 16:00:00
_______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
