Re: vs2005 bug status?
- From: "GaryDean" <GaryDean@xxxxxxxxxxxxxxxxx>
- Date: Tue, 17 Jan 2006 17:22:07 -0800
Yes, I think you are right. If you generated everything in code you would
not have this problem.
--
Regards,
Gary Blakely
"Gabriel Magaña" <no-spam@xxxxxxxxxxx> wrote in message
news:eak9OXuGGHA.3320@xxxxxxxxxxxxxxxxxxxxxxx
>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" <GaryDean@xxxxxxxxxxxxxxxxx> wrote in message
> news:eZj96tsGGHA.2000@xxxxxxxxxxxxxxxxxxxxxxx
>> 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" <erik@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:1roxsldl0pwfp$.dlg@xxxxxxxxxxxxxxxxxx
>>> 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).
>>
>>
>
>
.
- Follow-Ups:
- Re: vs2005 bug status?
- From: "Yuan Ren[MSFT]"
- Re: vs2005 bug status?
- References:
- vs2005 bug status?
- From: GaryDean
- Re: vs2005 bug status?
- From: Erik Funkenbusch
- Re: vs2005 bug status?
- From: GaryDean
- Re: vs2005 bug status?
- From: Gabriel Magaņa
- vs2005 bug status?
- Prev by Date: Re: Instantiate TableAdapter at Runtime
- Next by Date: Re: who came up with JavaScript language syntax?
- Previous by thread: Re: vs2005 bug status?
- Next by thread: Re: vs2005 bug status?
- Index(es):
Relevant Pages
|