vs2005 bug status?

G

GaryDean

A couple of weeks ago I reported a bug in vs2005 where it corrupted projects
converted from vs2003 if a 2003 dataset were modified or recreated. Steven
Cheng [MSFT] was able to recreate the bug. I reported the bug and Steven
said he was also going to report the bug.

From a practical standpoint this bug prevents migration of projects from
vs2003 to vs2005 because if 2003 dataadapters and datasets can't be changed,
any large project is unmaintainable. In other words it's a realy realy bad
bug.

Is there a way to find the status of this problem? when will it be fixed?
Unless I'm willing to manually convert over 700 2003 dataadapter : dataset
pairs to 2005 GridView : ObjectDataSource : Datasets the vs2005 product is
useless to me (and I just forked out 2 grand for an MSDN license to get it).
 
G

Guest

Gary,
I am sure Steven's intentions were good but you can't totally depend on
others to submit your "bugs" for you.

Go to the product feedback site, search first to see who else has reported
this,
and if none, submit it yourself. Check the notification option to be able to
follow up on progress.
Peter
 
E

Erik Funkenbusch

A couple of weeks ago I reported a bug in vs2005 where it corrupted projects
converted from vs2003 if a 2003 dataset were modified or recreated. Steven
Cheng [MSFT] was able to recreate the bug. I reported the bug and Steven
said he was also going to report the bug.

From a practical standpoint this bug prevents migration of projects from
vs2003 to vs2005 because if 2003 dataadapters and datasets can't be changed,
any large project is unmaintainable. In other words it's a realy realy bad
bug.

Is there a way to find the status of this problem? when will it be fixed?
Unless I'm willing to manually convert over 700 2003 dataadapter : dataset
pairs to 2005 GridView : ObjectDataSource : Datasets the vs2005 product is
useless to me (and I just forked out 2 grand for an MSDN license to get it).
Click to expand...

While I can't speak for anyone at Microsoft, my experience is that they
don't typically fix bugs in Visual Studio with any kind of timeliness. I
understand there may be a VS2005 service pack this summer, and if that's
the case, you probably couldn't hope for a fix before then.

You might want to look into an automatic way to do what you need done, such
as using tools like Perl to process your code looking for common patterns.

That may suck, but unless your bug affects a LARGE number of MS's
customers, they're not going to go through a pach process (which is quite
lengthy and costly) for a single flaw, especially if there's a workaround
(even though such a workaround may be uncomfortable for you).
 
O

Otis Mukinfus

A couple of weeks ago I reported a bug in vs2005 where it corrupted projects
converted from vs2003 if a 2003 dataset were modified or recreated. Steven
Cheng [MSFT] was able to recreate the bug. I reported the bug and Steven
said he was also going to report the bug.

From a practical standpoint this bug prevents migration of projects from
vs2003 to vs2005 because if 2003 dataadapters and datasets can't be changed,
any large project is unmaintainable. In other words it's a realy realy bad
bug.

Is there a way to find the status of this problem? when will it be fixed?
Unless I'm willing to manually convert over 700 2003 dataadapter : dataset
pairs to 2005 GridView : ObjectDataSource : Datasets the vs2005 product is
useless to me (and I just forked out 2 grand for an MSDN license to get it).
Click to expand...

I feel your pain Gary, but I'm wondering if you threw your VS 2003
installation away. The two will run side by side without a problem,
so why not do new development with VS 2005 and maintenance on the
existing app with VS 2003? If the project is as large as you say, and
it works, why convert it?


Otis Mukinfus
http://www.otismukinfus.com
http://www.tomchilders.com
 
G

GaryDean

like I said, I reported the bug.

--
Regards,
Gary Blakely
Peter Bromberg said:
Gary,
I am sure Steven's intentions were good but you can't totally depend on
others to submit your "bugs" for you.

Go to the product feedback site, search first to see who else has reported
this,
and if none, submit it yourself. Check the notification option to be able
to
follow up on progress.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com




GaryDean said:
A couple of weeks ago I reported a bug in vs2005 where it corrupted
projects
converted from vs2003 if a 2003 dataset were modified or recreated.
Steven
Cheng [MSFT] was able to recreate the bug. I reported the bug and
Steven
said he was also going to report the bug.

From a practical standpoint this bug prevents migration of projects from
vs2003 to vs2005 because if 2003 dataadapters and datasets can't be
changed,
any large project is unmaintainable. In other words it's a realy realy
bad
bug.

Is there a way to find the status of this problem? when will it be
fixed?
Unless I'm willing to manually convert over 700 2003 dataadapter :
dataset
pairs to 2005 GridView : ObjectDataSource : Datasets the vs2005 product
is
useless to me (and I just forked out 2 grand for an MSDN license to get
it).
Click to expand...
Click to expand...
 
G

GaryDean

Well, I think it's a bad bug that keeps anyone from converting a 2003
project. It makes 2005 only good for new projects.

Is it only me that thinks that's bad?

--
Regards,
Gary Blakely
Erik Funkenbusch said:
A couple of weeks ago I reported a bug in vs2005 where it corrupted
projects
converted from vs2003 if a 2003 dataset were modified or recreated.
Steven
Cheng [MSFT] was able to recreate the bug. I reported the bug and
Steven
said he was also going to report the bug.

From a practical standpoint this bug prevents migration of projects from
vs2003 to vs2005 because if 2003 dataadapters and datasets can't be
changed,
any large project is unmaintainable. In other words it's a realy realy
bad
bug.

Is there a way to find the status of this problem? when will it be
fixed?
Unless I'm willing to manually convert over 700 2003 dataadapter :
dataset
pairs to 2005 GridView : ObjectDataSource : Datasets the vs2005 product
is
useless to me (and I just forked out 2 grand for an MSDN license to get
it).
Click to expand...

While I can't speak for anyone at Microsoft, my experience is that they
don't typically fix bugs in Visual Studio with any kind of timeliness. I
understand there may be a VS2005 service pack this summer, and if that's
the case, you probably couldn't hope for a fix before then.

You might want to look into an automatic way to do what you need done,
such
as using tools like Perl to process your code looking for common patterns.

That may suck, but unless your bug affects a LARGE number of MS's
customers, they're not going to go through a pach process (which is quite
lengthy and costly) for a single flaw, especially if there's a workaround
(even though such a workaround may be uncomfortable for you).
Click to expand...
 
G

GaryDean

Why convert it? To take advantage of the new features.

haven't thrown away 2003, just can't use 2005

--
Regards,
Gary Blakely
Otis Mukinfus said:
A couple of weeks ago I reported a bug in vs2005 where it corrupted
projects
converted from vs2003 if a 2003 dataset were modified or recreated.
Steven
Cheng [MSFT] was able to recreate the bug. I reported the bug and Steven
said he was also going to report the bug.

From a practical standpoint this bug prevents migration of projects from
vs2003 to vs2005 because if 2003 dataadapters and datasets can't be
changed,
any large project is unmaintainable. In other words it's a realy realy
bad
bug.

Is there a way to find the status of this problem? when will it be fixed?
Unless I'm willing to manually convert over 700 2003 dataadapter : dataset
pairs to 2005 GridView : ObjectDataSource : Datasets the vs2005 product
is
useless to me (and I just forked out 2 grand for an MSDN license to get
it).
Click to expand...

I feel your pain Gary, but I'm wondering if you threw your VS 2003
installation away. The two will run side by side without a problem,
so why not do new development with VS 2005 and maintenance on the
existing app with VS 2003? If the project is as large as you say, and
it works, why convert it?


Otis Mukinfus
http://www.otismukinfus.com
http://www.tomchilders.com
Click to expand...
 
G

Gabriel Magaña

I think it only affects people who had the code auto generated by VS2003 no?
I have not noticed any problem with my projects.... But I also happen to no
t have the DB code autogenerated (ie, data adapters created through the GUI
etc...)

GaryDean said:
Well, I think it's a bad bug that keeps anyone from converting a 2003
project. It makes 2005 only good for new projects.

Is it only me that thinks that's bad?

--
Regards,
Gary Blakely
Erik Funkenbusch said:
A couple of weeks ago I reported a bug in vs2005 where it corrupted
projects
converted from vs2003 if a 2003 dataset were modified or recreated.
Steven
Cheng [MSFT] was able to recreate the bug. I reported the bug and
Steven
said he was also going to report the bug.

From a practical standpoint this bug prevents migration of projects from
vs2003 to vs2005 because if 2003 dataadapters and datasets can't be
changed,
any large project is unmaintainable. In other words it's a realy realy
bad
bug.

Is there a way to find the status of this problem? when will it be
fixed?
Unless I'm willing to manually convert over 700 2003 dataadapter :
dataset
pairs to 2005 GridView : ObjectDataSource : Datasets the vs2005 product
is
useless to me (and I just forked out 2 grand for an MSDN license to get
it).
Click to expand...

While I can't speak for anyone at Microsoft, my experience is that they
don't typically fix bugs in Visual Studio with any kind of timeliness. I
understand there may be a VS2005 service pack this summer, and if that's
the case, you probably couldn't hope for a fix before then.

You might want to look into an automatic way to do what you need done,
such
as using tools like Perl to process your code looking for common
patterns.

That may suck, but unless your bug affects a LARGE number of MS's
customers, they're not going to go through a pach process (which is quite
lengthy and costly) for a single flaw, especially if there's a workaround
(even though such a workaround may be uncomfortable for you).
Click to expand...
Click to expand...
 
G

Gabriel Magaña

You could always post the link to the bug report here to have people vote
for on it if it's affecting them...

GaryDean said:
like I said, I reported the bug.

--
Regards,
Gary Blakely
Peter Bromberg said:
Gary,
I am sure Steven's intentions were good but you can't totally depend on
others to submit your "bugs" for you.

Go to the product feedback site, search first to see who else has
reported
this,
and if none, submit it yourself. Check the notification option to be able
to
follow up on progress.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com




GaryDean said:
A couple of weeks ago I reported a bug in vs2005 where it corrupted
projects
converted from vs2003 if a 2003 dataset were modified or recreated.
Steven
Cheng [MSFT] was able to recreate the bug. I reported the bug and
Steven
said he was also going to report the bug.

From a practical standpoint this bug prevents migration of projects from
vs2003 to vs2005 because if 2003 dataadapters and datasets can't be
changed,
any large project is unmaintainable. In other words it's a realy realy
bad
bug.

Is there a way to find the status of this problem? when will it be
fixed?
Unless I'm willing to manually convert over 700 2003 dataadapter :
dataset
pairs to 2005 GridView : ObjectDataSource : Datasets the vs2005 product
is
useless to me (and I just forked out 2 grand for an MSDN license to get
it).
Click to expand...
Click to expand...
Click to expand...
 
G

GaryDean

Yes, I think you are right. If you generated everything in code you would
not have this problem.

--
Regards,
Gary Blakely
Gabriel Magaña said:
I think it only affects people who had the code auto generated by VS2003
no? I have not noticed any problem with my projects.... But I also happen
to no t have the DB code autogenerated (ie, data adapters created through
the GUI etc...)

GaryDean said:
Well, I think it's a bad bug that keeps anyone from converting a 2003
project. It makes 2005 only good for new projects.

Is it only me that thinks that's bad?

--
Regards,
Gary Blakely
Erik Funkenbusch said:
On Sat, 14 Jan 2006 17:16:48 -0800, GaryDean wrote:

A couple of weeks ago I reported a bug in vs2005 where it corrupted
projects
converted from vs2003 if a 2003 dataset were modified or recreated.
Steven
Cheng [MSFT] was able to recreate the bug. I reported the bug and
Steven
said he was also going to report the bug.

From a practical standpoint this bug prevents migration of projects
from
vs2003 to vs2005 because if 2003 dataadapters and datasets can't be
changed,
any large project is unmaintainable. In other words it's a realy realy
bad
bug.

Is there a way to find the status of this problem? when will it be
fixed?
Unless I'm willing to manually convert over 700 2003 dataadapter :
dataset
pairs to 2005 GridView : ObjectDataSource : Datasets the vs2005
product is
useless to me (and I just forked out 2 grand for an MSDN license to get
it).

While I can't speak for anyone at Microsoft, my experience is that they
don't typically fix bugs in Visual Studio with any kind of timeliness.
I
understand there may be a VS2005 service pack this summer, and if that's
the case, you probably couldn't hope for a fix before then.

You might want to look into an automatic way to do what you need done,
such
as using tools like Perl to process your code looking for common
patterns.

That may suck, but unless your bug affects a LARGE number of MS's
customers, they're not going to go through a pach process (which is
quite
lengthy and costly) for a single flaw, especially if there's a
workaround
(even though such a workaround may be uncomfortable for you).
Click to expand...
Click to expand...
Click to expand...
 
Y

Yuan Ren[MSFT]

Hi Gary,

Thanks for posting!

I have checked the information about the bug. Unfortunately, since the bug
is not critical as security issue, there is no available hot fix. But I
think it will be fixed on the next Service Pack.

I appreciate your understanding. And thanks for you submit you feedback!

Regards,

Yuan Ren [MSFT]
Microsoft Online Support
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

vs2005 clobbers converted project 5
VS2005 major development bug 16
VS2003 versus VS2005 data adapters: Auto-generated update commands generate parameter errors? 7
VS2005 Web Project - No DLL for Nunit 8
Binding sources question in Vs2005 2
Underwhelm by VS2005 52

Top