Nesting Trans within Try block produces syntax errors.

I am experiencing some baffling behavior with a generated script in SQL Server.
I inserted a column which requires the table to be dropped and recreated.  I automatically generated a script to perform this task on deployment.  This script contained a transaction (but no rollback).

It worked but when a modification was made to the script showing an additional new column, the script errored during execution and did not rollback.  So I added a try-catch block to the script.  Now I get three syntax errors so the script won't run.  But when I comment out the Begin and End Try and Catch there are no syntax errors.  I do not see what the issue is.

This was the code as generated by SQL Server 2008R2

	BEGIN TRANSACTION
		CREATE TABLE dbo.Tmp_GlobalLogging_ActionLog
			(
			ActionID int NOT NULL IDENTITY (1, 1),
			SubjectCN varchar(100) NOT NULL,
			PageCertSubject varchar(200) NULL,
			LogInDate datetime2(7) NOT NULL,
			PageLocation varchar(1000) NOT NULL,
			Client_IP_Address varchar(50) NULL
			)  ON [PRIMARY]
		GO
		ALTER TABLE dbo.Tmp_GlobalLogging_ActionLog SET (LOCK_ESCALATION = TABLE)
		GO
		SET IDENTITY_INSERT dbo.Tmp_GlobalLogging_ActionLog ON
		GO
		IF EXISTS(SELECT * FROM dbo.GlobalLogging_ActionLog)
			INSERT INTO dbo.Tmp_GlobalLogging_ActionLog (ActionID, SubjectCN, LogInDate, PageLocation, Client_IP_Address)
				SELECT ActionID, SubjectCN, LogInDate, PageLocation, Client_IP_Address FROM dbo.GlobalLogging_ActionLog 
		GO
		SET IDENTITY_INSERT dbo.Tmp_GlobalLogging_ActionLog OFF
		GO
		DROP TABLE dbo.GlobalLogging_ActionLog
		GO
		EXECUTE sp_rename N'dbo.Tmp_GlobalLogging_ActionLog', N'GlobalLogging_ActionLog', 'OBJECT' 
		GO
		ALTER TABLE dbo.GlobalLogging_ActionLog ADD CONSTRAINT
			PK_saic_reg_Action_Log PRIMARY KEY CLUSTERED 
			(
			ActionID
			) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

		GO
		COMMIT TRAN

Select allOpen in new window

This is the code as Modified

BEGIN TRY
	BEGIN TRANSACTION
		CREATE TABLE dbo.Tmp_GlobalLogging_ActionLog
			(
			ActionID int NOT NULL IDENTITY (1, 1),
			SubjectCN varchar(100) NOT NULL,
			PageCertSubject varchar(200) NULL,
			LogInDate datetime2(7) NOT NULL,
			PageLocation varchar(1000) NOT NULL,
			Client_IP_Address varchar(50) NULL,
			GLVersion varchar(10)
			)  ON [PRIMARY]
		GO
		ALTER TABLE dbo.Tmp_GlobalLogging_ActionLog SET (LOCK_ESCALATION = TABLE)
		GO
		SET IDENTITY_INSERT dbo.Tmp_GlobalLogging_ActionLog ON
		GO
		IF EXISTS(SELECT * FROM dbo.GlobalLogging_ActionLog)
			INSERT INTO dbo.Tmp_GlobalLogging_ActionLog (ActionID, SubjectCN, LogInDate, PageLocation, Client_IP_Address)
				SELECT ActionID, SubjectCN, LogInDate, PageLocation, Client_IP_Address FROM dbo.GlobalLogging_ActionLog 
		GO
		SET IDENTITY_INSERT dbo.Tmp_GlobalLogging_ActionLog OFF
		GO
		DROP TABLE dbo.GlobalLogging_ActionLog
		GO
		EXECUTE sp_rename N'dbo.Tmp_GlobalLogging_ActionLog', N'GlobalLogging_ActionLog', 'OBJECT' 
		GO
		ALTER TABLE dbo.GlobalLogging_ActionLog ADD CONSTRAINT
			PK_saic_reg_Action_Log PRIMARY KEY CLUSTERED 
			(
			ActionID
			) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

		GO
		COMMIT TRAN
	END TRY
	BEGIN CATCH
		ROLLBACK TRAN
		GO
	END CATCH

Select allOpen in new window

These are the errors

Msg 102, Level 15, State 1, Line 33
Incorrect syntax near 'PRIMARY'.
Msg 102, Level 15, State 1, Line 2
Incorrect syntax near 'TRY'.
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near 'CATCH'.

Select allOpen in new window

They refer to the line with primary, the line with "end try", and the line with "End Catch"

I don't understand what I am doing wrong here.  I've tried adding semi colons after the TRYs and the TRANSs.  This made no difference.  I thought it might not be permissable to use DDL within a Try-Catch block but MS technet example at this site http://technet.microsoft.com/en-us/library/ms179296(v=SQL.105).aspx shows the the use of DDL with the try catch block.
Does anyone have a clue as to the problem