Jitbit Software :: Forum

	9/5/2008 7:41:32 PM permalink
pnwfcu Posts 4	What are some recommendations on things to do, and especially not to do, when adding our own custom code, in order to make future upgrades from JitBit work with minimal problems? I'm thinking partial classes for the code behind files would probably solve a lot of potential problem, but what about the aspx markup? How about modifying existing database tables? Should I leave them be and just create resolution tables for all relations instead? edited by pnwfcu on 9/5/2008
	9/6/2008 6:14:44 AM permalink
jitbit Posts 712	yes, using partial classes for codebehind is the best option. as for the aspx files - we recommend using some simple file-comparision tool (for example, the one included with Total Commander file manager) to detect the changes/ Also I suggest you keep a non-modified versin of the source codes somewhere, which makes it very easy to determine what aspx-files have changed with the release (by simply sorting the files list by date).
pages: 1

|