Jan 7

Written by: Dylan Barber
1/7/2010 2:26 PM 

Okay with some excitement I downloaded the new Beta of the DNN blog – and since it comes with the great big warning in red from Antonio.

“Needless to say (but I'll say it anyway; in fact, I’ll make it bold and red as well), this is a BETA, and as such it is not supported and it should not be deployed in production environments. This is for test purposes ONLY. So, to re-iterate, if you screw up, sorry pal, you’re on your own.”

I decided to be smart and try it on my test install first. After all I didn’t want to mess up this blog.

 

My test install runs the same as this site DNN 05.02.00 and the Blog 3.5.1.

My first attempt was to install the new beta right over the old Blog. From the word go this caused some problems. My first clue was the nice SQL Provider warning.

‘SQL Execution resulted in following Exceptions: System.Data.SqlClient.SqlException: Incorrect syntax near '.'. Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon. Incorrect syntax near '.'. Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) if not exists (select * from dbo.sysobjects where id = object_id(N'dbo.Blog_Tags') and OBJECTPROPERTY(id, N'IsUserTable') = 1) BEGIN CREATE TABLE dbo.Blog_Tags( TagID int IDENTITY(1,1) NOT NULL, Tag nvarchar(255) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, Slug nvarchar(255) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, Active bit NOT NULL, PortalID int NULL, CONSTRAINT dbo.PK_Blog_Tags PRIMARY KEY CLUSTERED ( TagID ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] CREATE NONCLUSTERED INDEX dbo.IX_Blog_Tags_PortalID ON dbo.Blog_Tags ( PortalID ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = OFF) ON [PRIMARY] END’

Not a big deal but did worry me that maybe I would have to reinstall to get my blog back on this test install.

Thankfully this wasn’t the case I uninstalled the blog  then reinstalled the 3.5.1 Blog and everything worked again. If the Blog is uninstalled or has never been installed then installing the Blog 4.0.0 Beta 2 then the blog module works very well and installs fine.

Overall I like where the new blog module is going.