Visual Studio 2005 Stable ?

[Carlos]

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.

 

[Gabriele G. Ponti]

http://lab.msdn.microsoft.com/vs2005/golive/

 

[Peter van der Goes]

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.

While VS2005 Beta 2 appears to me to be stable (no one person can test
everything), you need to follow the link provided by Gabriele and read the
license carefully. Note especially the clauses on no support and no
guarantee that features you use now will actually be included in the release
version.
Only you can assess whether the risk (which you are assuming 100%) is worth
the convenience of using Serial Comm class in Beta2.

 

[Jon Skeet [C# MVP]]

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.

If you need to release the app before version 2.0 is properly released,
you *can't* use 2.0 legally.

 

[Willy Denoyette [MVP]]

If you need to release the app before version 2.0 is properly released,
you *can't* use 2.0 legally.

Sure you can, provided you have filed a Go-live license.

Willy.

 

[Guest]

To answer the first question: Yes, it seems extremely stable. I have seen a
few minor glitches in the April CTP (currently working with June CTP), but
nothing that is a showstopper for me.

Now, to the legal aspects. Under GoLive, you have the ability to release
ASP.NET apps. If you would like to use SQL Server 2005, you have limited
license for SQL Server 2005 Express. If you are building other types of
applications, check out the Go Live to ensure you are legal.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

 

[Marina]

We tried using VS2005 for winforms development back over the winter. It had
so many problems that it was completely unusable as far as getting any real
development done, littered with bugs. Back in March we switched gears and
went back to 2003. The fact that the release date kept being pushed back
really underscored the problems.

That's not to say it hasn't gotten somewhat better since. Or if you are
doing something completely different, or not pushing the limits of the
product, it might be fine.

 

[Jon Skeet [C# MVP]]

Sure you can, provided you have filed a Go-live license.

Oops - looks like I didn't understand the Go Live concept properly.
However, it still looks like for client apps which are distributed to
third parties, it's less than ideal - the OP won't be able to
distribute the framework itself, telling customers to get it
themselves.

Of course, we don't know the details of what the OP's app does or who
it's for...

 

[Willy Denoyette [MVP]]

Oops - looks like I didn't understand the Go Live concept properly.
However, it still looks like for client apps which are distributed to
third parties, it's less than ideal - the OP won't be able to
distribute the framework itself, telling customers to get it
themselves.

Of course, we don't know the details of what the OP's app does or who
it's for...

The Go-Live concept is IMO primarily meant for webserver applications not
realy for client applications, that's why they don't allow you to distribute
the framework. Note also that Go-Live is only for Beta2, later drops aren't
covered by the license.

Willy.

 

[Dick Grier]

Hi,

Do you have Visual Studio 2003? If so, then I'd suggest that you use
another library (such as DesktopSerialIO from my homepage), and release
your product now. Then, port it to VS 2005 using the Ports.IO namespace for
later update, say after the first of the year. The changes required for VS
2005 will be small. As others have pointed out, if you use VS2005, you are
taking a risk -- and you aren't supposed to release any product that uses
the Beta anyway.

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 4th
Edition ISBN 1-890422-28-2 (391 pages) published July 2004. See
www.mabry.com/vbpgser4 to order.

 

[Rob R. Ainscough]

One has to be close to insane to put out Beta anything in a production
environment -- client/server or whatever.