Scenario 1:
You do not change the wcco source code in any way. You reference its DLL from, or include it in your own source code.

If your code does not have a GUI, you don’t have to do anything.

If you code does have a GUI, put the following text snippet in the About box:

Includes OSI Certified Open  Source Software code from the book “Cryptography for Visual Basic: A Programmer’s Guide to the CryptoAPI” by Richard Bondi, published by John Wiley and Sons, Inc. (www.wiley.com/compbooks/bondi). Copyright © 2000 John Wiley & Sons, Inc. and others All Rights Reserved.

Scenario 2:
You make some small changes to the code, like optimizing a routine or two, cusomizing how it initializes, etc.

Well, the letter of the license requires you to proceed as if you had made substantive changes to the code (see below). But if you don’t tell, I won’t ask; you can proceed as in scenario 1.

Scenario 3:
You make substantive changes to the code, like incorporating new classes, adding enhancements like support for more data formats, etc..

In addition to doing what is described in scenario 1, the license requires you to document your changes briefly in the source code, in Exhibit A of the license.

The license also requires you to make your changes available to the world. In other words, you need to make the modified WCCO source code available to the world. There are two ways to do this:

• Put the modified source code on an ftp or Web site somewhere, and put its URL in the notice of scenario 1 as well as in Exhibit A.
• Add your changes to the original source code, located currently at the OpenAve.Net, an open source community development portal.

If you add your code at openave.net, you don’t have to mess with maintaining a permanent home for your code. You’ll also get bug reports from other users trying out your code.