> Besides, if Adobe wants to claim the exclusive right to
> define CFML (vs NA's BD, or the CFML engines out there), then
> they should step up and define the language more rigorously
> than "CF is what we just did".
Why should they bother, when it's clear they don't have to?
Dave Watts, CTO,
ple who cut our paychecks what
they want. It drives me crazy sometimes.
~Brad
-Original Message-
From: Aaron Rouse [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 12, 2008 11:42 AM
To: CF-Talk
Subject: Re: What are the Necessary Code Changes for Migrating from 6.1
to 8?
Microsoft nev
Microsoft never has problems with their products, simply undocumented
"features" :) Seriously though, I have only met one CF shop that
supposeably never had a bug with their outputted product. They however
invested an enormous amount of time in documentation/specs before every
writing a line of
> No, I'm not claiming to never have made a mistake. I'm saying that a
> mistake that is detected by the customer shows poor quality control.
Still sounds to me like actor-observer bias... I have yet to see any
company that's not had problems discovered by customers after the
release of a product.
On Mon, Mar 10, 2008 at 9:05 PM, Russ <[EMAIL PROTECTED]> wrote:
> Automated testing isn't always possible, especially when you are dealing
> with enterprise applications with millions of lines of code.
Sure it is possible. And large enterprise applications are the most
critical to have full auto
> From: s. isaac dealey [mailto:[EMAIL PROTECTED]
> Uhuh... and in order for this statement to make sense, you would have
to claim that you have never, ever made a decision, documented it, and
then discovered *later* that it had an impact you hadn't expected.
Shocking!
No, I'm not claiming to ne
> > Sounds to me like there's an expectation that the folks
> > doing the beta for new versions will be more
> > superhuman than everyone else.
>
> But the folks running the beta are not the ones responsible for
> discovering what the vendor changed! If you think we're all mad at the
> beta test
Ah, just wondered on that. I think a group at our work has a CF6 app that
they can not take ot CF7 due to some change with verity. Something about
copying files from one box to another, but maybe it is they are stuck on CF5
due to a change. I honestly do not recall enough of the details just tha
; From: Aaron Rouse [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 11, 2008 5:59 PM
> To: CF-Talk
> Subject: Re: What are the Necessary Code Changes for Migrating from 6.1 to
> 8?
>
> I know it can be done but I have yet to encounter a place running more
> than
> one version o
I know it can be done but I have yet to encounter a place running more than
one version of CF and actually most are not even willing to buy another
version of CF after their first initial purchase. Now if someone has an app
that works specifically on an older version of CF, do they get the option
Aaron Rouse wrote:
> True, but I might be completely wrong on this but I thought if someone made
> an ASP.NET application on say the 2.0 Framework that if the server was
> brought to the 3.5 Framework that the application would still run under the
> 2.0, so that would prevent potential errors relat
True, but I might be completely wrong on this but I thought if someone made
an ASP.NET application on say the 2.0 Framework that if the server was
brought to the 3.5 Framework that the application would still run under the
2.0, so that would prevent potential errors related to a version change on
t
own homework by studying that documentation.
Thanks
Mark
-Original Message-
From: s. isaac dealey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 11, 2008 12:41 AM
To: CF-Talk
Subject: Re: What are the Necessary Code Changes for Migrating from 6.1
to 8?
> You can'
While I feel your pain, CF6.1 was released when? You've been running
your code on an app server that's been upgraded three times already, so
I wouldn't fault Adobe overly much. Sorry to be blunt...
Steve "Cutter" Blades
Adobe Certified Professional
Advanced Macromedia ColdFusion MX 7 Developer
_
Russ wrote:
> I think this is where .NET might have an edge, as I believe that .ASPX pages
> are compiled, so compile time errors are found quicker, unlike CF, where you
> won't see even compile time errors until you actually invoke the template.
That just depends on how you develop and deploy yo
> Automated testing isn't always possible, especially when you
> are dealing with enterprise applications with millions of
> lines of code.
In that case, honestly, how do you even know that the code works right now?
All you know is that it does something that doesn't generate a visible
error, an
On Mon, Mar 10, 2008 at 9:05 PM, Russ <[EMAIL PROTECTED]> wrote:
> I think this is where .NET might have an edge, as I believe that .ASPX pages
> are compiled, so compile time errors are found quicker, unlike CF, where you
> won't see even compile time errors until you actually invoke the templa
> You can't always simulate every possible client action on a staging
> server. Sometimes the changes are such that they fail in very specific
> instances.
Sounds to me like there's an expectation that the folks doing the beta
for new versions will be more superhuman than everyone else.
--
s.
> The issue is not that there might be problems running the new version,
> but that the vendor has not properly documented the changes between
> versions. I don't think they should be required to maintain a
> "version x to version x + 2" set of issues, but a comprehensive list
> of compatibility-r
> -Original Message-
> From: Russ [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 11 March 2008 2:05 PM
> To: CF-Talk
> Subject: RE: What are the Necessary Code Changes for Migrating from 6.1
> to 8?
>
>
> Automated testing isn't always possible, especi
ch 10, 2008 11:21 PM
> To: CF-Talk
> Subject: Re: What are the Necessary Code Changes for Migrating from 6.1 to
> 8?
>
> Isn't the point of edge cases to find these types of situations, and
> document them? This speaks volumes to why automated testing is so crucial.
> Note, I s
Testing is very important, and I do not want to do anything to discount it, but
it has been my experience that it has limitations and it is not going to catch
every issue. I have found that it is not wise for a developer to rely on
testing methodologies, whatever they may be, to help them; they
Isn't the point of edge cases to find these types of situations, and
document them? This speaks volumes to why automated testing is so crucial.
Note, I said automated tests not unit tests. Unit tests are important, no
doubt about it, but when dealing with a language such as ColdFusion,
especially n
CF-Talk
> Subject: RE: What are the Necessary Code Changes for Migrating from 6.1 to
> 8?
>
> > I completely agree. I have no problem adapting to the
> > changes - if I knew what the changes were. It's the
> > possibility of unexpected changes not being discovered unti
> I completely agree. I have no problem adapting to the
> changes - if I knew what the changes were. It's the
> possibility of unexpected changes not being discovered until
> we upgrade production servers.
I agree that it would be better if Adobe provided this documentation, but
why in any ca
ECTED]
Sent: Monday, March 10, 2008 4:04 PM
To: CF-Talk
Subject: RE: What are the Necessary Code Changes for Migrating from 6.1
to 8?
Sorry if this was mentioned already, but what about the Code Analyzer in
the
CFAdmin?
Rich
~|
EMAIL PROTECTED] DTN
DTN. FARM SMARTER.www.dtn.com
-Original Message-
From: Gaulin, Mark [mailto:[EMAIL PROTECTED]
Sent: Monday, March 10, 2008 3:58 PM
To: CF-Talk
Subject: RE: What are the Necessary Code Ch
Sorry if this was mentioned already, but what about the Code Analyzer in the
CFAdmin?
Rich
~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;1
ibility-related changes for "version x to version x + 1" is
entirely reasonable to expect. IMHO.
Thanks
Mark
-Original Message-
From: s. isaac dealey [mailto:[EMAIL PROTECTED]
Sent: Monday, March 10, 2008 4:41 PM
To: CF-Talk
Subject: Re: What are the Necessary Code Chang
> Who releases a major revision of a language platform without a
> exhaustive change log? Even Microsoft, who every developer loves to
> hate, has this information available for .NET. Adobe is billing CF 8
> as a drop-in replacement for earlier versions of MX. If there's no
> other option beside
> Are you referring to the "Tag changes since ColdFusion 5" and
> "Function changes since ColdFusion 5" sections in the CFML reference?
> Or is there a different section that I should be looking at?
Yeah, that's probably it -- I was probably just misremembering the label.
--
s. isaac dealey ^
So far, we have
* QuerySetCell
* LDAP queries
* inside of
* Encrypt and Decrypt nuances
Doesn't sound like there's a complete list anywhere from Adobe. Does this
strike anyone else as just ridiculous? Who releases a major revision of a
language platform without a exhaustive change log?
New item we recently discovered. It wasn't an issue with 7, but is an
issue with 8, especially in view of the documentation. We have a
password that we 'encrypt'ed into the db, using 6.1. We later 'decrypt'
the password for use with a cfexecute call.
In 6.1, the Decrypt() function took two argu
Are you referring to the "Tag changes since ColdFusion 5" and "Function changes
since ColdFusion 5" sections in the CFML reference? Or is there a different
section that I should be looking at?
Nate
>I believe there's a "what's new" in the language reference for each
>version in both the livedo
We had to change all of our LDAP calls to be secure or else they would fail
in CF8
On Fri, Mar 7, 2008 at 5:23 PM, Nathan Wells <[EMAIL PROTECTED]> wrote:
> I posted this issue on Adobe's forums a couple of days ago, but I haven't
> had any (good) responses.
>
> I recently started testing our cod
I believe there's a "what's new" in the language reference for each
version in both the livedocs and the optional doc set you can install
with the server. I'm actually a bit surprised that you're getting errors
on QuerySetCell when moving up from 6.1 to 8. I know that they added an
argument, I've j
custom error handler that shoots off
alerts to you whenever something breaks.
Russ
> -Original Message-
> From: Nathan Wells [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 07, 2008 6:33 PM
> To: CF-Talk
> Subject: Re: What are the Necessary Code Changes for Migrating
>Nate I understand your frustration we have approx 500 Legacy CF application
>from CF5 we are migrating to CF8, and we've been dealing with daul versions
>for at least 3 years now... Any rate enough about that, have you taken
>advantage of the code analyzer in the CF administrator? While not perfec
Nate I understand your frustration we have approx 500 Legacy CF application
from CF5 we are migrating to CF8, and we've been dealing with daul versions
for at least 3 years now... Any rate enough about that, have you taken
advantage of the code analyzer in the CF administrator? While not perfect it
3,000 template system, and the only change we had to worry about was
removing the tags inside blocks. (this did not apply
to 'break' inside 'case' script statements, where it is necessary)
Steve "Cutter" Blades
Adobe Certified Professional
Advanced Macromedia ColdFusion MX 7 Developer
40 matches
Mail list logo
