Re: New Project Strategy: develop in 1.1 then migrate to 2.0 just before going live

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Jeff,

I've been using VS.Net 2005 for about a year now, since beta 1 I believe.
Beta versions had certain bugs in them, but were essentially stable. I have
never experienced any performance problems with it. I believe most of the
perceived performance problems were due to issues related to the uninstall
of previous beta versions. The upgrade process to the next beta (and finally
to the release version) has been highly complex, involving separate
uninstalls of various components in a certain order prior to installing the
newer version. If these procedures were not followed exactly, problems
occurred. Some of these problems manifested themselves as slow performance.

I have also seen quite a few more complaints about the new ASP.Net than
about other types of projects, such as Windows Forms, Services, and class
libraries. I have yet to do any ASP.Net work with the new Visual Studio, so
I can't say anything about that. But I have written quite a few other
projects, including Windows Forms, Services, and class libraries, without
any performance issues.

In addition, I have observed that VS.Net 2005 is far superior to VS.Net 2003
in many ways, too many to enumerate here, except to mention a few of the
more obvious improvements. Intellisense is much improved. Refactoring is a
real time-saver. Support for standards, in particular those involving XML is
incredible. And DTDs are used for error-checking and intellisense, which
makes a heck of a lot of sense.

I wouldn't go back to VS.Net 2003 for any reason, other than to maintain
legacy (1.1) applications.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.

"Jeff" <A@xxxxx> wrote in message
news:OivYZYzFGHA.376@xxxxxxxxxxxxxxxxxxxxxxx
> Re:
> << It's not our job to "sway" you >>
>
> Well, yes, of course not. But I'm looking to learn from some of you who
> have *not* been complaining. Maybe you have not observed the bugs - maybe
> you just aren't saying anything.
>
>
>
>
>
> "Gabriel Magana" <noone@xxxxxxxxxx> wrote in message
> news:OAfQjUzFGHA.1312@xxxxxxxxxxxxxxxxxxxxxxx
>> Well, I'm not gonna give you the free lunch you seek (you have to try
>> VS2005 out for yourself), but I can say that the bugs I have run into are
>> worth it for the many benefits that VS2005 brings.
>>
>> It's not our job to "sway" you... I'm sure there are people still using
>> VS6 because there are too many bugs in subsequent releases, but it is
>> their choice... It's more of a cost/benefit analysis you have to do
>> according to your own values/tolerance/etc...
>>
>> For example, just yesterday I fixed a long-standing layout bug in one of
>> our aspx pages just because of the collapsible tags in the VS2005 HTML
>> editor. The collapsible tags feature, in conjunction with the new
>> integrated HTML code formatter, allowed me to greatly simplify how the
>> HTML was displayed, making the syntax error very simple to catch. This
>> was an error that I had spent searching for at least a full day with
>> VS2003... But the VS2005 came with some bugs, including some pretty big
>> ones when it comes to deployment of web sites and also a very annoying
>> bug in which VS2005 checks into source control files under the /bin
>> directory when clearly, nothing in that folder should be checked into
>> source control. Is it worth the upgrade? Absolutely, even through there
>> are bugs, the benefits hugely outweight the annoyances for me.
>>
>> You have to make a similar evaluation and decision, based on your needs.
>>
>> "Jeff" <A@xxxxx> wrote in message
>> news:O4gJhKzFGHA.3176@xxxxxxxxxxxxxxxxxxxxxxx
>>> RE:
>>> << Have you actually tried it?... >>
>>>
>>> No, because I have work to do. And no, I'm not flaming or being
>>> negative. I'm a *huge* fan of Microsoft. I also have a lot of time
>>> constraints and simply don't have the time to screw around with a
>>> product which, given all of the chatter in the varous Microsoft NGs, was
>>> apparently rushed to market (or at least not fully developed when
>>> released). It appears that one one must be willing to deal with slow
>>> performance, random "freezing", machine crashes, etc. Given the volume
>>> of reports I think it's reasonable to conclude that I would likely
>>> experience similar symptoms.
>>>
>>> So while I'm looking to play it safe I also don't want to be obviously
>>> and unnecessarily cautious. So I guess I'd be swayed to go with VS 2005
>>> right away if a number of people responded to my post here claiming that
>>> they were totaly happy with VS 2005 and that they *never* experience any
>>> of the frequently reported "buggy" behaviour.
>>>
>>> -Jeff
>>>
>>>
>>>
>>>
>>> "Nicholas Paldino [.NET/C# MVP]" <mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote
>>> in message news:upNpcyyFGHA.2652@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Not only that, but you are pretty much going to miss out on a good
>>>> amount of functionality which VS.NET 2005 provides.
>>>>
>>>> Have you actually tried it? I ask because you say apparent...
>>>>
>>>> --
>>>> - Nicholas Paldino [.NET/C# MVP]
>>>> - mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>
>>>> "Stefan Nuxoll" <netkid91@xxxxxxxxx> wrote in message
>>>> news:11sbichjio3719a@xxxxxxxxxxxxxxxxxxxxx
>>>>> Jeff wrote:
>>>>>> Looking for your highly subjective opinions (from those of you who
>>>>>> have been working extensively with VS 2005).
>>>>>>
>>>>>> I have a client that needs/wants a complete rewrite of an existing
>>>>>> application. I will be proposing a .NET Windows application with a
>>>>>> supporting SQL Server database. It will likely take 4-5 months before
>>>>>> we roll out the first production version.
>>>>>>
>>>>>> Because of the apparent issues with VS 2005 (poor performance,
>>>>>> unpredictable and generally buggy behaviour), I am thinking it might
>>>>>> make sense to develop this app in VS.NET 2003/.NET 1.1. Then, around
>>>>>> the time we're ready to roll out the first production version,
>>>>>> migrate it to .NET 2.x just before going live.
>>>>>>
>>>>>> I say 2.x because Microsoft has plans to release a service pack for
>>>>>> it mid-way through 2006, so we might have a minor version number
>>>>>> change at that time. Also, it appears that the service pack from
>>>>>> Microsoft, if released mid-year, will stabilize things so we can
>>>>>> [hopefully] have a smooth transition to 2.x just before going live.
>>>>>>
>>>>>> Does this strategy make sense? Thoughts? Opinions?
>>>>>>
>>>>>> Thanks!
>>>>> This makes some sense, however doing something in this fashion is not
>>>>> recommended as some things may go haywire during the conversion
>>>>> process that you would need to fix. I find it easier just to deal
>>>>> with VS 2005 and make it with .NET 2.0 to start.
>>>>
>>>>
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Button events stopped working
    ... > Most bugs will go away in VS.net 2005. ... Try the recent beta, you will like ... If you don't set event properties in the html, ... Design View is the one who does it. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: freebsd naming of releases
    ... > a good amount of support behind the idea of releasing more often, ... > suited for widespread testing as an official beta is. ... > The introduction of these features brought about new edge cases and bugs. ...
    (freebsd-current)
  • Re: Does Microsoft Still Support MSVC V6?
    ... There are many doors. ... enter the right context for it to make sense. ... I just uninstalled the office beta last night and went back to Office 2000. ... testing meant "look for the bugs". ...
    (microsoft.public.vc.mfc)
  • Re: Delphi 8 doesnt work with some Developer Express components
    ... The first thing I was struck by (in going to the main Borland site), ... A 'click here' to use the public beta Java client. ... get your bugs fixed, and how it's the only supported way to report bugs, ... And this is HONESTLY how Borland DEMANDS that customers report bugs? ...
    (borland.public.delphi.non-technical)
  • Re: Spaces!!?
    ... The real fix pack is coming as a "Service Release". ... The way to report bugs is to use Help>Send Feedback. ... your post goes straight into the Microsoft bug ... You think this thing is rough now, you should have seen it in beta ...
    (microsoft.public.mac.office.word)