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.

Is there any way to keep up the website with the nightly build ?  (Mono Support )

Viewed 3859 time(s), 4 post(s) 1/23/2013 6:26:44 PMby super
super

super

1/23/2013 6:26:44 PM
Is there any easy way to keep up the website with the nightly build ?

I picked the current nighty build for my website but still reporting bugs that are in the official release of 4.7 and current nightly build as well now that when I report bugs and you guys fix it and provide solution to next build - what if it is a database update fix or anything else ? how am I supposed to keep up wit the nightly build ?

FYI....I have not modified any code or not added any custom code in the website, just few changes in layout / design and personalized it a little bit ...does that means I have to download every nighty build and do all the changes in every build every week ?
This content has not been rated yet. 
6018 Reputation 709 Total posts
khorvat

khorvat

1/24/2013 1:57:17 PM
Hi,

basically you have to follow our best practices regarding custom projects explained in Building a custom ASP.NET project based on MonoXBuilding a custom Web part and most important article Upgrading to new MonoX version.

So first thing that you need to do is not to change MonoX files (I'm not 100% clear if you did that so I need to ask) but add your own, you can copy MonoX files and change them, and second thing is to use some kind of source control to monitor changes between files, so you follow the practice described in the upgrading article and update only MonoX core/engine and not your files, if anything important changes you can see the diff by using source control. After we push a nightly build you will have to download it, extract the package and follow above procedure.

Let me know if you need more information.

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
super

super

1/24/2013 2:38:50 PM
Well for any user to use monox project there will be some minimal changes like branding the website, etc..what I am planning to keep - no custom coding.

I used last week's friday nightly build for my website Jan 18, 2013.. but since nightly build is updated twice a week - I will have to download and update everything week two times and do the same changes for branding on the new build ?

My another question is...for example I am using Jan 18, 2013 and you pushed a new build - there could be a chance that there are database changes / additions in new one - is it ok to skip any build ? or I can't ? since I am assuming the upgrade script takes updates the script from last build database and when any build is skipped, the sql server will throw an error if it doesn't find anything that was skipped since if new fields/tables were introduced in that skipped build are required for updating ?

Or I can skip any build and use anu nightly build and when the installation screen is ON, I choose updating from previous version instead going with install as new database ?
This content has not been rated yet. 
6018 Reputation 709 Total posts
khorvat

khorvat

1/25/2013 8:31:58 AM
Hi,

first of all let me point out that you don't need to update twice a week, you need to check the change log and see if there is something that is of major importance to you and only then upgrade.

I used last week's friday nightly build for my website Jan 18, 2013.. but since nightly build is updated twice a week - I will have to download and update everything week two times and do the same changes for branding on the new build ?
You should never change MonoX files directly (especially ones in MonoX folder), you should copy them to your location and then change them in order to be able to upgrade and not lose your work. If we do change something on those copied pages these are probably demo pages and you shouldn't worry about it. If we change some other functionality in MonoX Core and you update to nightly build it will be updated for you without any additional effort involved.

My another question is...for example I am using Jan 18, 2013 and you pushed a new build - there could be a chance that there are database changes / additions in new one - is it ok to skip any build ? or I can't ? since I am assuming the upgrade script takes updates the script from last build database and when any build is skipped, the sql server will throw an error if it doesn't find anything that was skipped since if new fields/tables were introduced in that skipped build are required for updating ?
In case you skip few, or whole month of, builds you should take a look at the DBVersion in Version table and then you go to the scripts folder in MonoX and start from your version up to the latest one in order to have a valid database scheme. 

Or I can skip any build and use anu nightly build and when the installation screen is ON, I choose updating from previous version instead going with install as new database ?
No, there is no upgrade option in MonoX installation wizard, at least not that kind of upgrade. There is only an option to point MonoX app to existing database that you used from previous MonoX installation.

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts