<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Could anybody actually using VS 2005 comment on whether installing the Orcas CTP would solve this?<BR>
<BR>
<A href="http://www.microsoft.com/downloads/details.aspx?FamilyId=1E902C21-340C-4D13-9F04-70EB5E3DCEEA&displaylang=en">http://www.microsoft.com/downloads/details.aspx?FamilyId=1E902C21-340C-4D13-9F04-70EB5E3DCEEA&displaylang=en</A><BR>
<BR>
This is the community preview of the C# 3 extensions, made available as an extension to VS 2005.<BR><BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR><BR><BR><BR> <BR>> Date: Thu, 26 Mar 2009 01:27:42 -0400<BR>> From: teravus@gmail.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] C# 3.0 vs .Net 2<BR>> <BR>> Our issue here isn't mono support :) Mono has 3.0 support since<BR>> 1.9.1. It's our support of Visual Studio 2005 as a build tool.<BR>> <BR>> Visual Studio 2005 is the tool that doesn't understand code in C# 3.0 :).<BR>> <BR>> Visual Studio 2008 will generate a 2.0 assembly from 3.0 code.<BR>> Visual Studio 2005 will fail to build.<BR>> <BR>> As far as I really know.. the only reason to support Visual Studio<BR>> 2005 right now is for people who have Visual Studio 2005 Standard,<BR>> Pro, or Team licenses. Visual Studio 2008 Express is freely<BR>> downloadable and available and Mono is quite happy with 3.0 syntax<BR>> <BR>> Sincerely<BR>> <BR>> Teravus<BR>> <BR>> On 3/26/09, Frisby, Adam <adam@deepthink.com.au> wrote:<BR>> ><BR>> ><BR>> ><BR>> > If we consider a shift to .NET 3, I’d like to also propose utilizing the new<BR>> > Socket members that .NET 3 introduced – there is some in there for high<BR>> > performance ASync socketing which perform significantly better than previous<BR>> > ones in the kinds of situations we employ.<BR>> ><BR>> ><BR>> ><BR>> > (As long as Mono 2.0.2 has those implemented of course – but it shouldn’t be<BR>> > hard for the, they could at least just make them a splint to the old<BR>> > methods)<BR>> ><BR>> ><BR>> ><BR>> > Adam<BR>> ><BR>> ><BR>> ><BR>> ><BR>> ><BR>> > From: opensim-dev-bounces@lists.berlios.de<BR>> > [mailto:opensim-dev-bounces@lists.berlios.de] On Behalf Of<BR>> > Ruud Lathrop<BR>> > Sent: Wednesday, 25 March 2009 11:34 AM<BR>> > To: opensim-dev@lists.berlios.de<BR>> > Subject: Re: [Opensim-dev] C# 3.0 vs .Net 2<BR>> ><BR>> ><BR>> ><BR>> ><BR>> > Visual Studio 2005 is using .NET 2.0/C# 2, only with some extending can you<BR>> > use some .NET 3/C# 3 features (WCF is the best known).<BR>> ><BR>> > It seems that Visual Studio 2008 is doing some tricks for you when you have<BR>> > a .NET 2.0 project, but use .NET 3/3.5 syntax. Like this:<BR>> ><BR>> > public string Test { get; set; }<BR>> ><BR>> > Just works in a .NET 2.0 project, same with lambda, while it is .NET 3/ C# 3<BR>> > specs<BR>> ><BR>> > Ruud<BR>> ><BR>> ><BR>> ><BR>> > On Wed, Mar 25, 2009 at 3:57 PM, Teravus Ovares <teravus@gmail.com> wrote:<BR>> ><BR>> > The problem with Lamda Expressions isn't compiling to IL 2.0.. it's<BR>> > compiling in Visual Studio 2005. Visual Studio 2005 will not compile<BR>> > Lamda Expressions at all.<BR>> ><BR>> > Regards<BR>> ><BR>> > Teravus<BR>> ><BR>> ><BR>> ><BR>> > On 3/25/09, Sean Dague <sdague@gmail.com> wrote:<BR>> > > Stefan Andersson wrote:<BR>> > > > Yo.<BR>> > > >=20<BR>> > > > =20<BR>> > > >=20<BR>> > > > Feeling a bit stupid here, but just realized that many C# 3.0 features =<BR>> > > (lambda expressions and inferred types, for example) compiles just fine t=<BR>> > > o the .Net 2 IL, so in practise, it can be used if the installed csc supp=<BR>> > > orts it.<BR>> > > >=20<BR>> > > > =20<BR>> > > >=20<BR>> > > > What I'm saying is that we can probably start using some C# 3.0 feature=<BR>> > > s already even on mono (I guess) without moving from .Net 2.0. Question i=<BR>> > > s, what features?<BR>> > > >=20<BR>> > > >=20<BR>> > > > Could any mono person have a look at what C# 3.0 constructs are actuall=<BR>> > > y backwards compatible with .Net 2.0 on mono?<BR>> > ><BR>> > > One approach would be to make a new unit test that used some of those<BR>> > > features, then it would be easy for people to test with their<BR>> > > environment. I suspect mono 1.9.1 is still going to have issues, and we<BR>> > > haven't committed to dumping it yet (as that's what is shipping in the<BR>> > > latest stable release of Ubuntu, which a lot of people are using).<BR>> > ><BR>> > > The new Ubuntu release comes out in April with Mono 2.0.2, so we can<BR>> > > leave 1.9.1 behind in the near future.<BR>> > ><BR>> > > -Sean<BR>> > ><BR>> > > --=20<BR>> > > Sean Dague / Neas Bade<BR>> > > sdague@gmail.com<BR>> > > http://dague.net<BR>> > ><BR>> > ><BR>> > ><BR>> ><BR>> > > _______________________________________________<BR>> > > Opensim-dev mailing list<BR>> > > Opensim-dev@lists.berlios.de<BR>> > > https://lists.berlios.de/mailman/listinfo/opensim-dev<BR>> > ><BR>> > ><BR>> > ><BR>> > _______________________________________________<BR>> > Opensim-dev mailing list<BR>> > Opensim-dev@lists.berlios.de<BR>> > https://lists.berlios.de/mailman/listinfo/opensim-dev<BR>> ><BR>> ><BR>> > _______________________________________________<BR>> > Opensim-dev mailing list<BR>> > Opensim-dev@lists.berlios.de<BR>> > https://lists.berlios.de/mailman/listinfo/opensim-dev<BR>> ><BR>> ><BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR></body>
</html>