Re: First day with production development on D2005
- From: "a" <blwatters@xxxxxxx>
- Date: Wed, 1 Jun 2005 07:47:01 -0700
Atle,
I'm sure curious, but given the large number of problems folks appear
to be having with D2005, why wouldn't you have testing this in a
non-production environment prior to moving it on a production
system?
We installed D2005 on test machines and didn't have confidence
on even small projects. I won't just assume that installing it on a
new system, opening up a major D7 app, and expecting it to
operate flawlessly based on stories on the forums and our
experience with our test machines. I don't see how one could
use the system for more than a few hours/days and come up with
the plan to move it into production. At best, maybe one could
come up with a test plan of all the components, problems, etc.
which one might want tested before even considering moving to
a production system?
Thanks,
Brett
"Atle Smelvær" <atle@xxxxxxxxxxxxxx> wrote in message
news:429d85f1@xxxxxxxxxxxxxxxxxxxxxxxxx
> I've been testing D2005 now with demo projects on update 3 with small
> amounts of problems. Still very slow when opening forms/datamodules etc.
> the first time, but acceptable until the next major version.
>
> So I installed all commonly used components on our projects. FastReport,
> DevExpress components, Jedi VCL etc. This was done ok. Opened the project,
> and choose Win32. Got an error because a third party component was not
> installed but used in the form. Forgot on of the packages when installing.
> Ok, pressed Ignore All and then Close All. Bam! First exception in
> coreide90.bpl. Into the registry to activate the exceptiondiag90.bpl for
> Exception info sending to QC. For some strange reason this is not enabled
> default, and you have to change the blank value to "(Untitled)" for it to
> be loaded. Ok. Loaded D2005 again, and did the same routine. Bam! Got a
> send button, made a description in the wizard and entered login and
> password. Ok.. My same login has two different passwords for QC and login
> to the community site, took a shot at one of them (no way to change it in
> QC). Choose the wrong password, pressed back, entered new password and
> next. And there it was with "Error" at the top as before, but now both
> previous and next button was disabled. No way to come anywhere, and had to
> kill D2005. In again, do the same things over and now choose the right
> password. Ok, it was sendt finally. Back to the IDE to install the
> components missing. One of them was kbmMemTable. This one is split in one
> design package and one runtime. Compiling the runtime gave me no problems.
> But compiling the designtime after, gave a F2141 Bad file format:
> "kbmMemD9Run.dcp"
>
> Still, it did create the bpl and dcp file for the design time package. And
> there was no other existing kbmMemD9Run.dcp. It was renamed to D9 just for
> that purpose. So the previous build did create the one it was using, and
> there was no error or anything when building it. So this is an error
> somewhere in the compiler maybe.. Ok. Now we are up in 3 errors so far...
>
> Then I closed D2005, and got me a nice exception in coreid90.bpl again.
> Ok. Described it and sendt it to QC. After closing the exception, well I
> got me another exception.. This time inside exceptiondiag90.bpl. So the
> exception handler may have problems handling exceptions when closing
> D2005. Described where the error and sendt it. Now we are up in 5 errors..
> And I am getting very unconfortable with the whole IDE.
>
> Not giving up yet.
>
> Installed a second component to the palette. Just a small calendar,
> nothing special. But after this one got installed, whenever I tried
> choosing any component on the Tool Palette, the focus changed to
> sourceview and the component list dissappeared. Surprise!
>
> Removed the component again, and everything was normal. Checked the
> component, nothing special at all there, only thing is that it only
> registers one little component on its own group. Installed it again, and
> changed to embedded mode. Now it was working.. Changed to non embedded,
> and the components just disappear whenever I push them again. So this
> component could only be used with embedded modus, as it appears... This is
> very odd indead. And there is no error when installing or compiling the
> package. Only ordinary registering is performed in the package. And now
> I'm up in 6 obscurd things happening within 2 hours.
>
> It's been 2 hours now, and already I'm up in 4 QC reports (not reported
> everything yet).
>
> Oh. It's so nice to work with such a stable environment. And it's so nice
> of Borland to release it in the state they did, and even after 3 updates
> have it this way.
>
> Well, back to D7 we go again.
>
> -Atle
>
.
- Follow-Ups:
- Re: First day with production development on D2005
- From: Atle Smelvær
- Re: First day with production development on D2005
- References:
- First day with production development on D2005
- From: Atle Smelvær
- First day with production development on D2005
- Prev by Date: Re: Just random fixes with QC reports...
- Next by Date: Re: Just random fixes with QC reports...
- Previous by thread: Re: First day with production development on D2005
- Next by thread: Re: First day with production development on D2005
- Index(es):
Relevant Pages
|
