Development Process - Revision history

Anw: /* Development Environment */

2011-09-14T11:02:37Z

Development Environment

← Older revision		Revision as of 13:02, 14 September 2011
Line 4:		Line 4:
	* Visual SourceSafe Client		* Visual SourceSafe Client
	* A Local MySQL Database instance, configured with the latest Vision database		* A Local MySQL Database instance, configured with the latest Vision database
	* A Local IIS implementation.		* A Local IIS implementation, with a local copy of the ''CALIDUS'' Vision product.

	A Notepad++ installer is available on the shared project drive in P:\271321 - Vision\_Development\Development Tools\npp.5.8.1.Installer.exe.		A Notepad++ installer is available on the shared project drive in P:\271321 - Vision\_Development\Development Tools\npp.5.8.1.Installer.exe.

Anw at 11:01, 14 September 2011

2011-09-14T11:01:35Z

@@ Line 1: / Line 1: @@
 *Always change code though SourceSafe, after checking out the file first.
 *Always follow the examples of existing code in the project.
 *Always create generic ASP and JavaScript functions where possible. Add them to CommonASP.asp and Common.js respectively.

Anw: /* Committing Changes */

2011-05-09T13:04:50Z

Committing Changes

← Older revision		Revision as of 15:04, 9 May 2011
Line 13:		Line 13:
	'''Example:'''		'''Example:'''
	<pre>		<pre>
	272693/SW-7YYJEU for DHL/EMEA/CHEW - Added choice of employee; Added extended Export functionality (through to HTML-style XLS sheet).		272693/SW-7YYJEU for DHL/EMEA/CHEW - Added choice of employee;
	272694/SW-7YYJNV for DHL/EMEA/CHEW - Fixed bug created during testing regarding setting the user default values for the Productivity Settings selection.		Added extended Export functionality (through to HTML-style XLS sheet).
			272694/SW-7YYJNV for DHL/EMEA/CHEW - Fixed bug created during testing
			regarding setting the user default values for the Productivity Settings selection.
	</pre>		</pre>

Anw at 07:22, 9 May 2011

2011-05-09T07:22:25Z

← Older revision		Revision as of 09:22, 9 May 2011
Line 31:		Line 31:

	[[Category:Vision Overview]]		[[Category:Vision Overview]]
	[[Category:Vision Coding and Release\|030]]		[[Category:Vision Coding and Release Doc\|030]]
			[[Category:Vision Coding and Release]]

Anw at 14:06, 6 May 2011

2011-05-06T14:06:46Z

← Older revision		Revision as of 16:06, 6 May 2011
Line 31:		Line 31:

	[[Category:Vision Overview]]		[[Category:Vision Overview]]
	[[Category:Vision Coding and Release]]		[[Category:Vision Coding and Release\|030]]

Anw at 12:55, 22 April 2010

2010-04-22T12:55:49Z

← Older revision		Revision as of 14:55, 22 April 2010
Line 29:		Line 29:

	Remove any reference to the schema from the code – the schema (generically Productivity1) is identified at the top of the script. If this is ever changed (or multiple schemas are used for development and release), it will be easier to change if this is only at the top of the script once. If objects are being added to other schemata, either explicitly add the schema on the SQL by exception or create a new copy of the script for changes solely for that schema.		Remove any reference to the schema from the code – the schema (generically Productivity1) is identified at the top of the script. If this is ever changed (or multiple schemas are used for development and release), it will be easier to change if this is only at the top of the script once. If objects are being added to other schemata, either explicitly add the schema on the SQL by exception or create a new copy of the script for changes solely for that schema.

			[[Category:Vision Overview]]
			[[Category:Vision Coding and Release]]

Anw: /* Committing Changes */

2010-04-22T12:44:54Z

Committing Changes

← Older revision		Revision as of 14:44, 22 April 2010
Line 6:		Line 6:
	==Committing Changes==		==Committing Changes==
	When checking code back in, check the changes you have made using SourceSafe’s Show Differences function. Ensure that all changes are detailed when checking back in. The format for these comments should be:		When checking code back in, check the changes you have made using SourceSafe’s Show Differences function. Ensure that all changes are detailed when checking back in. The format for these comments should be:
	*{supimix ref}/{client ref} for {client}/{Area}/{site} – {Description}		<pre>{supimix ref}/{client ref} for {client}/{Area}/{site} – {Description}</pre>
	If there are multiple changes made for this log, separate them with semi-colons.		If there are multiple changes made for this log, separate them with semi-colons.

Anw at 12:44, 22 April 2010

2010-04-22T12:44:43Z

← Older revision		Revision as of 14:44, 22 April 2010
Line 12:		Line 12:

	'''Example:'''		'''Example:'''
			<pre>
	272693/SW-7YYJEU for DHL/EMEA/CHEW - Added choice of employee; Added extended Export functionality (through to HTML-style XLS sheet).		272693/SW-7YYJEU for DHL/EMEA/CHEW - Added choice of employee; Added extended Export functionality (through to HTML-style XLS sheet).

	272694/SW-7YYJNV for DHL/EMEA/CHEW - Fixed bug created during testing regarding setting the user default values for the Productivity Settings selection.		272694/SW-7YYJNV for DHL/EMEA/CHEW - Fixed bug created during testing regarding setting the user default values for the Productivity Settings selection.
			</pre>

	Ensure where possible that the descriptions are relevant to the users, as these will form the release notes later.		Ensure where possible that the descriptions are relevant to the users, as these will form the release notes later.
Line 24:		Line 23:

	When changes are complete, the SQL changes should be copied into the file		When changes are complete, the SQL changes should be copied into the file
			<pre>
	*P:\271321 - Vision\_Installers\Releases In Progress\LatestDBChanges.SQL		P:\271321 - Vision\_Installers\Releases In Progress\LatestDBChanges.SQL
			</pre>
	All table changes should preserve data, so tables should never be dropped, simply altered.		All table changes should preserve data, so tables should never be dropped, simply altered.

	Remove any reference to the schema from the code – the schema (generically Productivity1) is identified at the top of the script. If this is ever changed (or multiple schemas are used for development and release), it will be easier to change if this is only at the top of the script once. If objects are being added to other ~~schemas~~, either explicitly add the schema on the SQL by exception or create a new copy of the script for changes solely for that schema.		Remove any reference to the schema from the code – the schema (generically Productivity1) is identified at the top of the script. If this is ever changed (or multiple schemas are used for development and release), it will be easier to change if this is only at the top of the script once. If objects are being added to other schemata, either explicitly add the schema on the SQL by exception or create a new copy of the script for changes solely for that schema.

Anw: Created page with 'Always change code though SourceSafe, after checking out the file first. '''Note:''' To install sourcesafe run P:\VSS\NETSETUP.EXE Always follow the examples of existing code i...'

2010-04-22T11:08:34Z

Created page with '*Always change code though SourceSafe, after checking out the file first. '''Note:''' To install sourcesafe run P:\VSS\NETSETUP.EXE *Always follow the examples of existing code i...'

New page

*Always change code though SourceSafe, after checking out the file first.
'''Note:''' To install sourcesafe run P:\VSS\NETSETUP.EXE
*Always follow the examples of existing code in the project.
*Always create generic ASP and JavaScript functions where possible. Add them to CommonASP.asp and Common.js respectively.

==Committing Changes==
When checking code back in, check the changes you have made using SourceSafe’s Show Differences function. Ensure that all changes are detailed when checking back in. The format for these comments should be:
*{supimix ref}/{client ref} for {client}/{Area}/{site} – {Description}
If there are multiple changes made for this log, separate them with semi-colons.

If there are multiple logs, add the changes made for each log subsequently, in the same format.

'''Example:'''

272693/SW-7YYJEU for DHL/EMEA/CHEW - Added choice of employee; Added extended Export functionality (through to HTML-style XLS sheet).

272694/SW-7YYJNV for DHL/EMEA/CHEW - Fixed bug created during testing regarding setting the user default values for the Productivity Settings selection.

Ensure where possible that the descriptions are relevant to the users, as these will form the release notes later.

==Changing the Database==
All changes should be made to the local development database.

When changes are complete, the SQL changes should be copied into the file

*P:\271321 - Vision\_Installers\Releases In Progress\LatestDBChanges.SQL

All table changes should preserve data, so tables should never be dropped, simply altered.

Remove any reference to the schema from the code – the schema (generically Productivity1) is identified at the top of the script. If this is ever changed (or multiple schemas are used for development and release), it will be easier to change if this is only at the top of the script once. If objects are being added to other schemas, either explicitly add the schema on the SQL by exception or create a new copy of the script for changes solely for that schema.

Development Process - Revision history

Anw: /* Development Environment */

Anw at 11:01, 14 September 2011

Anw: /* Committing Changes */

Anw at 07:22, 9 May 2011

Anw at 14:06, 6 May 2011

Anw at 12:55, 22 April 2010

Anw: /* Committing Changes */

Anw at 12:44, 22 April 2010

Anw: Created page with '*Always change code though SourceSafe, after checking out the file first. '''Note:''' To install sourcesafe run P:\VSS\NETSETUP.EXE *Always follow the examples of existing code i...'

Anw: Created page with 'Always change code though SourceSafe, after checking out the file first. '''Note:''' To install sourcesafe run P:\VSS\NETSETUP.EXE Always follow the examples of existing code i...'