Carlos,
VS.NET 2005 itself has a few bugs in it (there is a nasty one about the
IDE not accepting non-alphanumeric input, like arrows, the return key, etc,
etc), as does .NET 2.0, but these are both still in beta. However, as far
as the framework is concerned, I would say it is pretty stable (I haven't
seen anything that is an absolute show stopper yet).
As for the API being stable, I would guess that what you see now is what
you will get later on when the framework comes out. However, you should
redistribute your application when the new framework comes out, because it
will be a different version number than you have now (you could keep the
beta framework installs out there, but I don't think that would be a good
idea).
Regarding the serial COMM class that is in .NET 2.0, I dislike it a
great deal. They went from a stream-based pull model to a push model with
events. My biggest gripe against this is not so much about getting events,
but rather, the fact that you can't use the connection anywhere a Stream is
expected (which would have been nice).
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard. caspershouse.co m
"Carlos" <cp@swa.com> wrote in message
news:up******** ******@TK2MSFTN GP14.phx.gbl...
I have to implement a application that use Serial COM ports and I was
thinking to use VS2005, but I wan to know is that is true that is stable ?
I heard that the release date is November 7 2005 and I have to release the
app in August 2005, I want to move to 2005 so I can use ths IO Serial COMM
class that come with the Framework 2.0, I was using a VB6 control but I
want to avoid that so I do not have to distribute and regiuster the ocx.
Thanks for any comment.