>On all but one contract I have worked on, I have used my own framework. The one exception, the client owned the license to the framework. So for me this has yet to be an issue.
>I suspect that if it ever was an issue, if the client wanted the source code, they would be required to purchase a license for the framework. A relatively inexpensive fee compared to mine... :)

I agree, Erik, this would be the way to go. Like you, I use my own framework but I also use a few third-party tools with license restrictions like I mentioned. I have never had a client that wanted source code, but figured this would be the way to handle it if it ever came up. As you say, a relatively small expense compared to the cost of the app.

BTW, if you are conveying ownership of your code to your client, you may want to take steps in your contract to insure that you retain the rights to your framework and other reusable pieces. Typically you might refer to these things as "background technology", previously developed by you, to which you retain rights, but which you license to your client to use non-exclusively in connection with the app you develop for them. If you relinquish ownership of the framework, a client could hypothetically claim copyright infringement against you if you use that same framework for another client. Probably would never happen, but you never know, especially if the next client turns out to be a competitor of the first one.