Is C# 2.0 fully implemented?

[Anders Borum [.NET/C# MCP]]

Hello!

A longer version of this posting was originally sent to the C# whidbey
newsgroup, but it seems like those newsgroups don't get much attention from
Microsoft.

I'm wondering on the status of C# 2.0 and whether it's been fully
implemented in the released betas of VS .NET or we can expect compilation
errors originating from an incomplete C# 2.0 compiler.

Thanks in advance!

--
With regards
Anders Borum / SphereWorks
Microsoft Certified Professional (.NET MCP)

[cody]

I know of a few syntax changes they made. For example something with
generics changed and they renamed a VB keyword for partial classes.

"Anders Borum [.NET/C# MCP]" <an****@sphereworks.dk> schrieb im Newsbeitrag
news:#o**************@TK2MSFTNGP09.phx.gbl...

Hello!

A longer version of this posting was originally sent to the C# whidbey
newsgroup, but it seems like those newsgroups don't get much attention from Microsoft.

I'm wondering on the status of C# 2.0 and whether it's been fully
implemented in the released betas of VS .NET or we can expect compilation
errors originating from an incomplete C# 2.0 compiler.

Thanks in advance!

--
With regards
Anders Borum / SphereWorks
Microsoft Certified Professional (.NET MCP)

[Abubakar]

I think its not done as the vs.net (or the framework 2.0) are still in the
beta 1 phase, so I think yes we can expect errors in the compiler.

Ab.

"Anders Borum [.NET/C# MCP]" <an****@sphereworks.dk> wrote in message
news:#o**************@TK2MSFTNGP09.phx.gbl...

Hello!

A longer version of this posting was originally sent to the C# whidbey
newsgroup, but it seems like those newsgroups don't get much attention from Microsoft.

I'm wondering on the status of C# 2.0 and whether it's been fully
implemented in the released betas of VS .NET or we can expect compilation
errors originating from an incomplete C# 2.0 compiler.

Thanks in advance!

--
With regards
Anders Borum / SphereWorks
Microsoft Certified Professional (.NET MCP)

[Anders Borum [.NET/C# MCP]]

Hello Cody

Thanks for the quick reply.

I know of a few syntax changes they made. For example something with
generics changed and they renamed a VB keyword for partial classes.

I've had some problems with generics - it seemed like the compiler
complained about conversion between different types etc. that didn't make
much sense (to me, atleast). Initially this cause a great deal of headache,
but I guess that's the price of using beta software.

Maybe I should post my findings to Microsoft .. probably a good idea.

However, posting on the Whidbey C# newsgroup makes no sense, as nobody seem
to me reading it.

--
With regards
Anders Borum / SphereWorks
Microsoft Certified Professional (.NET MCP)

[Willy Denoyette [MVP]]

"Anders Borum [.NET/C# MCP]" <an****@sphereworks.dk> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...

Hello Cody However, posting on the Whidbey C# newsgroup makes no sense, as nobody
seem
to me reading it.

What makes you think that?
I think your question is to general, be more specific. If you have and
compiler issues with generics, just explain with a code snip and compiler
output what the issues are.

Willy.

[Anders Borum [.NET/C# MCP]]

Hello!

What makes you think that? I think your question is to general, be more specific. If you have and
compiler issues with generics, just explain with a code snip and compiler
output what the issues are.

Well, the question was pretty straightforward I think, but I'm not going
into a debate about this. I guess the traffic here makes one pretty spoiled
..

Regardless, I got a few great answers - they're appreaciated.

--
With regards
Anders Borum / SphereWorks
Microsoft Certified Professional (.NET MCP)

[Frans Bouma [C# MVP]]

Anders Borum [.NET/C# MCP] wrote:

Hello Cody

Thanks for the quick reply.

I know of a few syntax changes they made. For example something with
generics changed and they renamed a VB keyword for partial classes.

I've had some problems with generics - it seemed like the compiler
complained about conversion between different types etc. that didn't make
much sense (to me, atleast). Initially this cause a great deal of headache,
but I guess that's the price of using beta software.

Maybe I should post my findings to Microsoft .. probably a good idea.

However, posting on the Whidbey C# newsgroup makes no sense, as nobody seem
to me reading it.

Bugs in whidbey should be posted in Ladybug:
http://lab.msdn.microsoft.com/produc...k/default.aspx

so they get noted, commented on and fixed. So if you run into an issue
with generics, please take the time to file a bug there.

Frans

--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

[Derrick Coetzee [MSFT]]

"Anders Borum [.NET/C# MCP]" <an****@sphereworks.dk> wrote:

I'm wondering on the status of C# 2.0 and whether it's been fully
implemented in the released betas of VS .NET or we can expect compilation
errors originating from an incomplete C# 2.0 compiler.

I don't work in the VS group, but I can tell you there are product groups
inside Microsoft which use Whidbey for all their building. This is a very
solid beta, and there are not likely to be significant changes to the
language beyond this point. (Of course, I don't promise you won't encounter
compiler bugs or see significant changes still, but I'd be surprised.) In
particular, generics seem to work fine, although if you haven't used any
form of generics before there is a bit of a learning curve. If there's any
particular problem you're experiencing, please post the details of it --
even a misleading compiler error can be considered a bug.
--
Derrick Coetzee, Microsoft Speech Server developer
This posting is provided "AS IS" with no warranties, and confers no rights.

[Anders Borum [.NET/C# MCP]]

Hello!

As per posting by Frans Bouma, I will double check again and file a bug,
which I'm not 100% sure it is - but it looks quite strange (perhaps because
I'm trying to bend generics in ways in which it was not designed - or
because I have limited experience with it - who knows :-).

Regardless, I'm going to take a stab at it.

Thanks again for all the replies to my original question!

--
With regards
Anders Borum / SphereWorks
Microsoft Certified Professional (.NET MCP)