| |
This is a collection of questions that come
up frequently enough that the answers become part of the documentation.
| Where's the manual? |
Sorry, there isn't one...
There is a Tutorial that steps through some of the
basic things you can do with Ecco Helpers, but it
assumes that you are very familiar with Ecco.
There is some documentation on GTD in the DaveG-GTD.ect
template.
|
| Why is there both a registration key and
then a username and option code? |
The registration key enables the installation
and copy protection software to run the application.
The copy protection is necessary due to the ease with
which .NET code can be reverse engineered. Without the
copy protection, it is trivial using tools supplied
with MS Visual Studio (or free on the web) to disassemble,
modify and then re-compile .NET applications. It is
even possible to easily convert to a different language
in the process. This is wonderful if you are within
a corporate firewall, not very good for commercial applications...
The username and option code is used to enable individual
options in the code. This allows us to bundle numerous
applications in the same executable and to enable just
the ones you have licensed. By bundling numerous applications
in the same package, we save a lot of effort on testing
and distribution. The registration key gets used once
for your computer and afterwards will enable any of
our applications that use the same key sequence. The
username and option code are stored in the AppSettings.dat
file that contains all your application settings. New
releases typically will have changes in the format of
the AppSettings.dat file and therefore will require
you to re-enter your username and option code to enable
the features you have licensed. |
| I downloaded your product, but I was not
able to install as it said I needed a .Net framework?
What is that? |
You need to install the .NET framework.
There are links on the download page, one to a marketing/technical
overview, and the other to a download of the framework
itself. In short, .NET is Microsofts's answer to Java's
J2EE, it provides consistent and very powerful capabilities
for web services, distributed applications, etc. In
(hopefully) developing a "successor" to Ecco I've felt
that the collaboration capabilities were some of the
most important places where Ecco needs to evolve. Ecco
was ahead of it's time, but the rest of the world is
now catching up. I based the new stuff on .NET (at least
to start) because creating acceptable consumer level
user interfaces in Java is so much more difficult. Ultimately
things like your synchronized file will use web services
(SOAP and XML based) for keeping everything unified.
The link to the download is
here, unfortunately it's really big. That's why
I chose to have people download it from Microsoft instead
of bundling it with my download. It would be simple
if it was distributed on a CD... |
|
|
