>I will be maintaining the source code and there shouldn't be a reason that the application should need to be maintained on a regular basis except fo upgrades. On this particular project I must provide the source code upon completion. One way would be to include a copy of Mere Mortals with the app. This company doesn't have IT staff and would more than likely just have someone modify my code if anything needed fixed. In this scenario I don't know how beneficial having a license would be, since they probably wouldn't spend the time learning it anyway.
>
>The license agreement states the following:
>
>1.3 Oak Leaf Enterprises grants you an unlimited, royalty-free right to distribute MM .NET assemblies along with software you create using MM .NET
>
>By this I was thinking that I could provide the assemblies along with my source code in a solution file. The references would then be invalid when the project was loaded, but they could repoint those references to the distributed assemblies. Then by rebuilding the project everything would work in order to make changes to my code, rebuild, and redeploy. They would never be able to see the Mere Mortal or use Mere Mortals to build objects, but they would be able to modify anything in my source without anything being broken.
>
>Is this a possible scenario?

Yes, given this scenario, they don't need a license for MM .NET.

Best Regards,