Re: Serious .NET Problem?
- From: Robert Giesecke <spam@xxxxxxxxx>
- Date: Sun, 17 Jul 2005 12:42:15 +0200
Kevin,
>I wonder if Chrome does... It does indeed...
> Anyway, the issue is that as a side-effect other languages are at a > disadvantage, despite the claims by Microsoft of all the other > language support.
You cannot blame them for making progressions. .Net 2.0 is not something that surprisingly came up yesterday. There were public betas available for *quite* some time. Draw your own conclusions from D.Net not having 2.0 support at this time.
If you are a .Net Developer, you should chose your tools carefully to be up to date.
I switched for .Net dev to VS.Net after getting mad upon my stupitity (I was dump enough to actually buy D8!).
It's been a while since and I won't look back again.
Now I even have an ObjectPascal inside VS, so I don't have to deal with missing metaclasses, virtual constructors etc. in C# anymore. :-)
I hope for you and any other developer being in the same position, that Borland changes its point about adding 2.0 for Dexter, I really do.
If not, you have two choices left (IMHO): Forget about this cool managed API for SQL 2005 or move to another development tool. (Which also intergates pretty well with SQL2005 ;-) )
I know, within the next hours there will be plenty of answers tearing my post apart. But maybe I could be at least of some help...
.
- Follow-Ups:
- Re: Serious .NET Problem?
- From: Kevin
- Re: Serious .NET Problem?
- From: Nick Hodges [TeamB]
- Re: Serious .NET Problem?
- References:
- Serious .NET Problem?
- From: Kevin
- Re: Serious .NET Problem?
- From: Lee Grissom
- Re: Serious .NET Problem?
- From: Kevin
- Serious .NET Problem?
- Prev by Date: Re: FastMM <-> MemCheck
- Next by Date: Re: FastMM <-> MemCheck
- Previous by thread: Re: Serious .NET Problem?
- Next by thread: Re: Serious .NET Problem?
- Index(es):
Relevant Pages
|
|