Imaging modifying classes and tables that contain scrambled code. How
would you know where to insert your modifications if the logic is not
readable? Can they scramble only part of a method? Is the scrambling
consistent between releases? Imagine upgrades if the next release of
the scrambled software doesn't use the same scrambled names. Imagine
reporting against scrambled field and table names. I would find the
scrambling approach annoying and begging for the development of a
descrambler.
Scrambling code puts all the support burden on the vendor. Can they
handle it? The Axapta community is known to fix Microsoft's and other
vendor bugs. I don't mind black-box add-ons, but Axapta's architecture
doesn't support it (yet) other than the kernel. I would like to see
more "process hooks" in Axapta rather than overriding methods to add
functionality. I can envision optional classes that are called (if they
exist) during a process.
Jim Chwaszczewski
[EMAIL PROTECTED]
________________________________________________________________________
Message: 4
Date: Fri, 3 Feb 2006 08:55:55 +0100
From: "Andrae, Tobias" <[EMAIL PROTECTED]>
Subject: AW: Axapta Code Protection - Source Scrambling
Hi Henrik,
this sounds nice indeed.
BUT: Would you like to be responsible for an Axapta project at a
customers site where important parts of the application are scrambled
because you, as the project leader, had to buy some scrambled 3rd party
modules? What about customizing those things after the installation,
let's say, two years after Kick-Off? I don't know ...
In my eyes one of the biggest strengths of Axapta is it's "open source"
idea. And after all - all of you (me included) have learned programming
in Axapta by reading some of the code provided...
Best regards, Tobias
--------------------------------------------------------
The content of this E-mail and any attached files is confidential, and may be subject
to certain privilege. This email is intended for the designated recipient(s) only.
If you have received this E-mail in error, please immediately contact the sender.
Pursuant to Treasury Circular 230, the IRS requires us to advise you that if this email (or any attachment) contains advice concerning any federal tax issue, it was not written or intended to be used, and may not be used, for the purpose of avoiding federal tax penalties.
WIPFLI LLP
Business experts. Right from the start.
--------------------------------------------------------
SPONSORED LINKS
| Computer part | Programming languages | Microsoft axapta |
| Support exchange |
YAHOO! GROUPS LINKS
- Visit your group "development-axapta" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
