Basically Documentation, Documentation, Documentation. Make sure your code makes no assumptions. (like that it is on windows, or that session.whatever exists) and throw good helpful errors if they don't.
Add a Readme, and examples. Ensure you specify the platforms / versions it been tested and those that it hasn't been.. Add docs like those at cflib.org to your UDFs. Make sure your cfcs have hints etc, for the automatic doc creation. Add comments / usage to your tags. Add a licence. Make sure there are is contact email address and/or web site address. Zip them all up. (and .gz if you are targeting Linux). Lots to do huh? WG -----Original Message----- From: Adam Wayne Lehman [mailto:[EMAIL PROTECTED] Sent: 06 June 2003 13:39 To: CF-Talk Subject: Packaging a CFC/CustomTag/UDF 4 distribution I'm looking for some best practices when packaging CF code for distribution. Like what to watch out for, how to make an install as easy as possible, what files to include, etc. Does anyone have any opinions or recommendations? Thanks in advance. Adam Wayne Lehman Web Systems Developer Johns Hopkins Bloomberg School of Public Health Distance Education Division ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
