Dear All,

Just wanted to inquire whether VS.NET 2005 Beta is more stable than the
VS.NET 2003 (using common features only as in case of a port) ?
Also when is right time (earliest) to port a product made in VS.NET 2003 to
the newer version and whether its redistributable is available or not ?


Thank You in advance
rawCoder

Hi Rawcoder,

See this thread which was yesterday in the VBNet newsgroup, and go to the
begin and don't look to much at the ending kind of chitchat just to make the
messages more clear.

http://tinyurl.com/5u386


Cor

Hi Cor,

Thanx for reply.

Sorry for not reading it earlier and wasting a post. (Actually the subject
didnt suggest the content and I unfortunately cant read all posts.)

btw, this tinyURL is really kool, I wonder why the idea isn't catching up.
Or may be I am missing something again.

Thanks again
rawCoder


"Cor Ligthert" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Rawcoder,
>
> See this thread which was yesterday in the VBNet newsgroup, and go to the
> begin and don't look to much at the ending kind of chitchat just to make
the
> messages more clear.
>
> http://tinyurl.com/5u386
>
>
> Cor
>
>

No Beta product exhibits stability of release products. You make it sound
as though you are having problems with VS 2003.

2005 is still in Beta1 which means there are still bugs being found and
fixed. Also, 2005 still has debug symbols in the code which help to locate
and diagnose errors. This also causes the code to run slower than release
code which has been fully optimized by the compiler.

--
Gerry O'Brien [MVP]
Visual Basic .NET(VB.NET)




"rawCoder" <(E-Mail Removed)> wrote in message
news:%23dmDs%(E-Mail Removed)...
> Dear All,
>
> Just wanted to inquire whether VS.NET 2005 Beta is more stable than the
> VS.NET 2003 (using common features only as in case of a port) ?
> Also when is right time (earliest) to port a product made in VS.NET 2003
> to
> the newer version and whether its redistributable is available or not ?
>
>
> Thank You in advance
> rawCoder
>
>

Hi rawcoder,

http://tinyurl.com/

Herfried does by instance not like this one because it does not stay
forever, however is that needed? And shorter links on Google does not work
for full threads and search.

I did some test about that datatable, have a look at that.

Cor

> Herfried does by instance not like this one because it does not stay
> forever, however is that needed?

I agree with the concern, especially since these post get archived by google
and such. But www.tinyurl.com does say they "never expire". Why believe
otherwise?

I am a big fan of tinyurl.
Greg

Could be a little bit faster though...

"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:eSCJ9O$(E-Mail Removed)...
> > Herfried does by instance not like this one because it does not stay
> > forever, however is that needed?
>
> I agree with the concern, especially since these post get archived by
google
> and such. But www.tinyurl.com does say they "never expire". Why believe
> otherwise?
>
> I am a big fan of tinyurl.
> Greg
>
>
>

Hey Gerry,

>>No Beta product exhibits stability of release products. You make it sound
>>as though you are having problems with VS 2003.

This may be true in general, but in the case of VS 2003 its a serious
question. The VS 2003 forms designer is an incredible mess of bugs and we
for one are champing at the bit for a reliable version so we can get on with
serious work instead of forever inventing workarounds and recovering design
information that VS simply chucks away seemingly at random

Cheers

Doug Forster

What kind of issues are you experiencing? We have been using 2003 from Beta
until now and I see no bugs with the forms designer.

Can you give me some examples that I can try out.

I do know that if you make changes to the code in the Designer Generated
section that it will be overwritten by VS. Visual Studio 2005 solves that
issue.

I'd like to try some of the things that you are seeing as bugs. Not that I
can fix them or have them fixed in 2003 if they are bugs but you can submit
these issues via product feedback to Microsoft so they can be looked at for
possible fixes in service packs.


--
Gerry O'Brien [MVP]
Visual Basic .NET(VB.NET)




"Doug Forster" <doug_ZAPTHIS_AT_ZAPTHIS_TONIQ_DOT_CO_DOT_NZ> wrote in
message news:eD$(E-Mail Removed)...
> Hey Gerry,
>
>>>No Beta product exhibits stability of release products. You make it
>>>sound as though you are having problems with VS 2003.
>
> This may be true in general, but in the case of VS 2003 its a serious
> question. The VS 2003 forms designer is an incredible mess of bugs and we
> for one are champing at the bit for a reliable version so we can get on
> with serious work instead of forever inventing workarounds and recovering
> design information that VS simply chucks away seemingly at random
>
> Cheers
>
> Doug Forster
>
>

oh there is bugs with the form designer we've had controls mysteriously
"disappear" by themselfs on compiles and other odd stuff like that then when
you go back to the form to look at it they are mysteriously missing on there
too like they never existed..


"Gerry O'Brien [MVP]" <gerry dot obrien at gmail dot com> wrote in message
news:(E-Mail Removed)...
> What kind of issues are you experiencing? We have been using 2003 from
> Beta until now and I see no bugs with the forms designer.
>
> Can you give me some examples that I can try out.
>
> I do know that if you make changes to the code in the Designer Generated
> section that it will be overwritten by VS. Visual Studio 2005 solves that
> issue.
>
> I'd like to try some of the things that you are seeing as bugs. Not that
> I can fix them or have them fixed in 2003 if they are bugs but you can
> submit these issues via product feedback to Microsoft so they can be
> looked at for possible fixes in service packs.
>
>
> --
> Gerry O'Brien [MVP]
> Visual Basic .NET(VB.NET)
>
>
>
>
> "Doug Forster" <doug_ZAPTHIS_AT_ZAPTHIS_TONIQ_DOT_CO_DOT_NZ> wrote in
> message news:eD$(E-Mail Removed)...
>> Hey Gerry,
>>
>>>>No Beta product exhibits stability of release products. You make it
>>>>sound as though you are having problems with VS 2003.
>>
>> This may be true in general, but in the case of VS 2003 its a serious
>> question. The VS 2003 forms designer is an incredible mess of bugs and we
>> for one are champing at the bit for a reliable version so we can get on
>> with serious work instead of forever inventing workarounds and recovering
>> design information that VS simply chucks away seemingly at random
>>
>> Cheers
>>
>> Doug Forster
>>
>>
>
>