MonoX support board

Start the conversation, ask questions and share tips and solutions with fellow developers.

Non-registered users can only browse through our support boards. Please register now if you want to post your questions. It takes a second and it is completely free. Alternatively, you can log in without registration using your credentials at major sites such as Google, Microsoft Live, OpenId, Facebook, LinkedIn or Yahoo.

Upgrade from 4.9 to 5.1  (Mono Support )

21482 put(a) pogledan, 9 odgovor(a) 28.3.2015. 15:15:03Kreirao(la) super
super

super

29.3.2015. 11:47:25
Question 1

So, I am upgrading from 4.9 to 5.1v.

If I don't worry about web files (chages I did in 4.9) and all I care about is using new 5.1 code files and upgrade my database from 4.9 to 5.1 successfully.

In 5.1 database there is no major changes?

I see the upgrade scripts are on two:

01. Create_AuditInfo

-- USE []
 
BEGIN TRANSACTION
BEGIN TRY
 
CREATE TABLE [dbo].[AuditInfo](
    [Id] [uniqueidentifier] NOT NULL,
    [UserId] [uniqueidentifier] NOT NULL,
    [AffectedEntityName] [nvarchar](250) NULL,
    [ActionDateTime] [datetime] NOT NULL,
    [ActionType] [int] NOT NULL,
    [ActionTypeName] [nvarchar](150) NULL,
    [ActionPerformedByUser] [nvarchar](250) NULL,
    [ActionData] [nvarchar](max) NULL,
    [ActionDataBinary] [varbinary](max) NULL,
    [DateCreated] [datetime] NOT NULL,
    [DateUpdated] [datetime] NOT NULL,
    [ConcurrencyTimeStamp] [timestamp] NULL,
    [IpAddress] [nvarchar](50) NULL,
    [UserAgent] [nvarchar](255) NULL,
    [Referrer] [nvarchar](500) NULL,
    CONSTRAINT [PK_AuditInfo] PRIMARY KEY CLUSTERED ([Id] ASC)
)
 
ALTER TABLE [dbo].[AuditInfo]  WITH CHECK ADD 
CONSTRAINT [FK_AuditInfo_aspnet_Users] FOREIGN KEY([UserId]) REFERENCES [dbo].[aspnet_Users] ([UserId]) ON DELETE CASCADE
ALTER TABLE [dbo].[AuditInfo] CHECK CONSTRAINT [FK_AuditInfo_aspnet_Users]
 
ALTER TABLE [dbo].[AuditInfo] ADD  CONSTRAINT [DF_AuditInfo_DateCreated]  DEFAULT (getutcdate()) FOR [DateCreated]
ALTER TABLE [dbo].[AuditInfo] ADD  CONSTRAINT [DF_AuditInfo_DateUpdated]  DEFAULT (getutcdate()) FOR [DateUpdated]
 
 
COMMIT TRANSACTION
--ROLLBACK TRANSACTION
END TRY
 
BEGIN CATCH
       SELECT ERROR_LINE() AS [Line], ERROR_MESSAGE() AS [Message],    
        ERROR_NUMBER() AS [Number], ERROR_SEVERITY() AS [Severity],
        ERROR_STATE() AS [State], ERROR_PROCEDURE() AS [Procedure]
        ORDER BY [Line];
       ROLLBACK TRANSACTION
END CATCH  
GO



02. DB_Version_Insert

Begin transaction
BEGIN TRY
 
    INSERT INTO [dbo].[Version]
           ([Id]
           ,[Version]
           ,[Comment]
           ,[UpgradeLog]
           ,[DateEntered])
     VALUES
           (newid()
           ,'5.1.40.5027'
           ,''
           ,GETDATE())
         
COMMIT TRANSACTION                             
END TRY
 
BEGIN CATCH
       SELECT
        ERROR_NUMBER() AS ErrorNumber,
        ERROR_SEVERITY() AS ErrorSeverity,
        ERROR_STATE() AS ErrorState,
        ERROR_PROCEDURE() AS ErrorProcedure,
        ERROR_LINE() AS ErrorLine,
        ERROR_MESSAGE() AS ErrorMessage;    
       ROLLBACK TRANSACTION
END CATCH      


Does that means there are no changes in 5.1 version in respect to database or tables, everything remains same?
Ovaj sadržaj još nije ocijenjen. 
6018 Reputacija 709 Ukupno objava
super

super

29.3.2015. 11:47:05
Question 2

The upgrade guidelines says "if you haven't added any new localization settings to the database, you can delete records form the tables LocalizationSource, LocalizationString and LocalizationBinary"

I never added anything in the localization, I do see a lot of default values in LocalizationSource table. So, should i delete all the data from these 3 tables and run the sql scripts for these 3 tables from "Import" folder?



    • LocalizationSource.sql "\MonoX\Installer\Sql\import\LocalizationSource.sql"
    • LocalizationString.sql  "\MonoX\Installer\Sql\import\LocalizationString.sql"
    • LocalizationBinary.sql  "\MonoX\Installer\Sql\import\LocalizationBinary.sql"
Ovaj sadržaj još nije ocijenjen. 
6018 Reputacija 709 Ukupno objava
super

super

29.3.2015. 11:49:00
Question 3

Where is "MonoX_Patch_4_9_40_4907_40_to_5_1_40_5065_40.zip"

What changes I need to apply?

How I know that I didn't apply this patch in 4.9?
Ovaj sadržaj još nije ocijenjen. 
6018 Reputacija 709 Ukupno objava
idrazic

idrazic

30.3.2015. 7:13:05
Hi super,

1. Yes, correct.
2. If you haven't used DB resource provider for localization, you don't have to do anything.
3. Click "Other Versions you can download" and you will see it. You don't need it if you used "MonoX_Patch_4_9_40_4907_40_to_5_1_40_5107_40.zip"

Regards,
Igor
Ovaj sadržaj još nije ocijenjen. 
1384 Reputacija 152 Ukupno objava
Terry

Terry

30.3.2015. 17:52:33
Any chance of updating the Microsoft Azure Web App Gallery to 5.1?  It is still 4.9.
Ovaj sadržaj još nije ocijenjen. 
65 Reputacija 7 Ukupno objava
idrazic

idrazic

31.3.2015. 9:44:35
Terry, please see my answer here.
Ovaj sadržaj još nije ocijenjen. 
1384 Reputacija 152 Ukupno objava
jagh1987

jagh1987

17.9.2015. 14:59:35
Hellow!

I am upgrading from 4.9 to 5.1v. I have a Monox previous website and I download "MonoX_Patch_4_9_40_4907_40_to_5_1_40_5107_40.zip", i make a previous backup of my website (my previous version runs perfect)... I unzip the 5.1 package files, copy, paste and overwrite the existing file over the 4.9 monox version.

When i finish, I have the next error: (see Image please)

some idea? post? please.
Ovaj sadržaj još nije ocijenjen. 
55 Reputacija 7 Ukupno objava
kiki

kiki

17.9.2015. 15:16:51
Hi can you please check the following blog post: http://monox.mono-software.com/blog/post/Mono/246/MonoX-CMS-upgrade-guidelines-v4-9-to-v5-1/ .

Also can you please open a new thread regarding this issue, this thread is a bit old.

Regards
Ovaj sadržaj još nije ocijenjen. 
10 Reputacija 2 Ukupno objava
jagh1987

jagh1987

18.9.2015. 15:07:33
I will check the info.
thanks...
Ovaj sadržaj još nije ocijenjen. 
55 Reputacija 7 Ukupno objava