Re: Wrapping up software

Stephan,
Thanks for your reply. I already have a big list of things i still need
to do, and it seems to be getting bigger and BIGGER!

Thanks again,
James.

ssamuel wrote:
James,

A few of the things that I've found useful in releasing software to end
users:

1. Go through every line and look at the exception list in the
framework docs for any methods you call. Understand when each is
thrown, and catch every (and only) exception that you can do something
with. Assume anything not caught will give the user a nasty error.
Catching SecurityException on a disk write is more important than
FileNotFoundException: good users tend to know where their files are
more often then they know that they don't have write permissions to the
department share.

2. Any time anything goes wrong, do the following: show the user a
polite message asking them to change their input (like sales, the
customer is always right; your software made the error, not them), and
write extensive debugging information some place where they'll be able
to get it to you.

3. Document everything public. If you're releasing a library, use the
built-in XML documentation that plugs into Intellisense. If you're
releasing non-library software, document from turning on the computer
through all normal tasks as bulleted how-to guides. Include a glossary
and screen shots. Don't bother writing mission statements and such
because no one reads them. Searchable online troubleshooting guides
have always seemed to be the most useful for my users.

4. Write and work around test cases that includes inane things, like
people unplugging USB drives in the middle of saving and the disk
filling up. Someone will be missing installation files, configuration,
proper access to the thing you assume everyone has access to, etc.

5. Don't wait for people to save configuration and don't make them load
it. Give them options like starting where they left off.

I'm sure there's more but that'll take you a long way.

I'm not sure about the usefulness of obfuscation: it's been proven
extensively that there is almost no security in obfuscation. Those who
want to reverse engineer always find a way. I prefer to patent and be
ready to defend my claim. Also, know your rights as a copyright holder;
anything original you do is copyrighted by you whether you explicitly
claim it or not.


HTH!


Stephan


pigeonrandle wrote:
Hi,
I have written several pieces of software and would like to hear any
thoughts anyone has on what measures i should take to ensure(!) its
stability and security at the hands of the *users*. I have obviously
put error handling in :O) but have heard of loads of other things i
could do like obfuscation and assembly signing.

All comments welcomed and appreciated in advance, so ... thanks!
James Randle.

.

Relevant Pages

  • Re: Wrapping up software
    ... A few of the things that I've found useful in releasing software to end ... I'm not sure about the usefulness of obfuscation: ... extensively that there is almost no security in obfuscation. ... know your rights as a copyright holder; ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: More on caching and logging
    ... or do you think it also includes corporate security ... have a much bigger problem than just computer security. ... If you want to look at the battery compartment" flip machine ... email to oshea dot j dot j at gmail dot com. ...
    (comp.sys.mac.system)
  • Re: More on caching and logging
    ... or do you think it also includes corporate security ... have a much bigger problem than just computer security. ... lab search it for whatever they search for down at the labs,, ... Now they only need to take it out of your sight for a minute - on some ...
    (comp.sys.mac.system)
  • Re: More on caching and logging
    ... or do you think it also includes corporate security ... have a much bigger problem than just computer security. ... possible for this intrusive device to be invented. ... important to know if Apple approves/cooperates than to know of the ...
    (comp.sys.mac.system)
  • Re: What is ClickOne?
    ... Note that by copying your typo here, I suddenly stopped being a gentleman too;-) ... You are not bigger than Microsoft, ... That's all I need to know about the value of obfuscation. ... In short I think we can say that: I think that obfuscating can't be done in .NET in a satisfying way and doesn't add value to source code, so I prefer to publish code openly; while you prefer to protect your work and make use of obfuscators in order to keep your source code more difficult to read, even though you're aware that 100% protection is not possible. ...
    (microsoft.public.dotnet.languages.csharp)
Loading