Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
This post comes to complete my webinar from yesterday, "Common Issues with Sitefinity Upgrades".
The webinar is currently available on demand for free view at the following link: http://www.sitefinity.com/developer-network/webinars/webinars-on-demand/common-issues-with-sitefinity-upgrades
There appeared a certain interest in the batch files I was using during the webinar. Those did the quick and dirty work of extracting the files, restoring the database, setting up IIS, granting the relevant IIS app pool service user full access to the website files and starting the browser.
After each sample a cleanup batch was run to undo all the above.
I'm supplying here an example of those scripts. Mind you that Rotem is the name of my machine (and consequently the name on which the SQL server is running).
Here is an example of such a script:
title Use this version...
SET BasePath=C:\Webinar\2. Sitefinity51 Without ProjectManager
SET RarFile=%BasePath%\2. Sitefinity51 Without ProjectManager.rar
SET WebsiteInIIS=Default Web Site
"C:\Program Files (x86)\Mozilla Firefox\firefox.exe"
-p FF_13 http:
SET bExtract = n
SET /P bExtract=
"Extract all files (y/[n = default])? "
%WINDIR%\System32\taskkill.exe /im Sitefinity.exe
Extracting. Please wait...
x -y -idq
Nothing to extract. Moving on.
Restoring database: %DataBaseName%
%WINDIR%\System32\inetsrv\appcmd.exe SET vdir
Granting Network Service access to the web folder...
:(OI)(CI)F /T /q
In order to restore the database, it calls another script, RestoreSitefinityFromBackup, which looks like this:
C:\Windows\System32\net.exe stop MSSQLSERVER
C:\Windows\System32\net.exe start MSSQLSERVER
Going to folder...
Running sql script...
"C:\Program Files\Microsoft SQL Server\110\Tools\Binn\SQLCMD.EXE"
-S Rotem -iRestoreSitefinityFromBackup.sql
Back to parent folder...
@dbname = $(DataBaseName)
/* 3. Restore */
DISK = $(DataBaseBackupFile)
The cleanup script looks something like:
title Cleaning up...
del /S /Q
rd /S /Q
title Clean-up complete.
Which calls DropDatabase.cmd:
-S Rotem -iDropDatabase.sql
Which runs DropDatabase.sql:
To follow-up the questions which were asked during the webinar, I've arranged them as Q&A's (I've merged some of the repeating/logically similar questions here).
Q: What if there are changes required in web.config, how would the upgrader know?
A: You have to manually merge the web.config between upgrades. We cannot guarantee that there are no third-party additions (except the default Sitefinity web.config), so we cannot merge automatically. (Also see the link in the previous answer).
Q: It would be nice to have a list of files that are touched to know which ones need to be uploaded again to server
A: You can find this in the documentation. We list new files so that you know what to include in your solution and deploy to the server.
Q: What exactly changes (except the version number) in the config files when we upgrade?
A: Generally it is only the versions that change. In rare cases if a configuration element is no longer valid and you have it in the configuration file it will be removed.
Q: Imports of module builder content from .xslx exported file, import of structure is there but not of content? Any plans for that?
A: We do not have immediate plans for this (5.4 or 6.0 versions), however our support staff can provide with sample project on the matter. The Dynamic Modules API is fully exposed and you can use it to import the data. Just open a ticket with this question.
Q: is there anything that can be done about the YSODs when someone upgrades but hasn't grabbed all the latest marketplace control references?
Can nuget be aware of the Telerik.Sitefinity.dll version so that a nuget package could be targeted to the user that way? I mean I don't want users on 5.2 getting notifications that there's an update to my assembly when getting it would cause YSOD on their app.
A: We've seen nugget do binding redirects to the assembly of Sitefinity in my bin folder. It has not been thoroughly tested it though.
Q: I recently updated from 5.1 to 5.3, and some of my code using Fluent API did not work properly afterwards. Apparently changes/corrections had been made regarding translations. Is it possible to be aware of such details before upgrading?
A: We usually announce breaking changes in the release notes. You should read them before upgrading. We try to keep seamless backward compatibility but sometimes there are breaking changes. We provide guidance in the release notes in those cases.
Q: Are the release notes easily available on your website? Before upgrading I only found the headlines of the new version.
A: You can view them in your account or in our forums, e.g. at this link.
Q: Just to clarify, you said that you support two versions back INCLUDING SERVICES PACKS? So if I am on Sitefinity 5.1 SP1 the farthest I can upgrade to is Sitefinity 5.2 SP1?
A: We only support upgrades two intermediate versions back (including service packs). You can run a longer-ranged upgrade directly, but it is not recommended. Between 5.1 and 5.3 there are not huge schema changes so this upgrade is possible. Furthermore for each version we may need to execute specific scripts to upgrade our database. If there are too many such scripts (e.g. 4.3 -> 5.3) your process may timeout, thus not executing all scripts. That is if the project being upgraded is not being run in debug mode. For the sake of the simplified demos presented in the webinar, 5.1 -> 5.3 upgrade was OK.
Q: how do we know to which version do intermediate upgrades exist, like for instance from v4.x>5.3, you'd step to v5.0 but that had an instant hotfix...
A: Follow the order of sticky threads here. Because there's always an exception, disregard hotfixes :-)
Q: Do you think you could enhance the project manager so it is aware of problem version updates? Like if someone tries to upgrade from 4.4-5.4 they'll get a popup warning or just outright prevent it?
A: We've been discussing this, but so far did not have the time to add it to the manager.
Q: how would you recommend upgrading a website with high traffic?
A: With caution :-)
A mirror staging platform would a good idea too, to produce the upgraded version and fully test it. Then deployment of upgraded modules, web.config and any other required changes can be relatively quick and hopefully pain free (minding that Sitefinity's config files, in the majority of the cases, need not be overridden). There may be no way other than taking the site down, but this may at least help reduce the down-time..
Q: Why does the Amazon S3 provider work 'properly' with a URL to the service, but Dropbox had to do a duplicate content sync? Why couldn't Sitefinity have the link to the Dropbox file (in a manner similar to the Amazon S3 implementation) instead of pulling it and and storing locally?
A: This is mainly because of how Dropbox works and authentication and authorization. Also note that Dropbox is not a storage provider, but a libraries synch with Drobpox provider.
Q: What is CloudBarry?
A: CloudBerry Explorer for Amazon S3 is a freeware Amazon S3 and Amazon Glacier client designed to run in Windows environment. S3 Explorer provides a user interface to Amazon S3 accounts, files and buckets allowing browsing, creating, and deleting files and buckets. Freeware Amazon S3 client by CloudBerry Lab comes with a full support for CloudFront (Amazon Content Delivery Network (CDN)). It includes a set of tools to manage CloudFront HTTP and Streaming Distributions, Public and Private content and more.
Q: Will you be supplying the files from these demos?
A: Sure, we will do a blog post about this.
See: This link (and then this).
Q: Will you share this training that we can review it later again?
A: All webinars are recorded and shared on the Webinars on Damand page. Sppecifically the Upgrades webinar is available here.
A: You're welcome!
Q: You are hitting or tapping the mic a lot.
A: Sorry about that, it was a sensitive table mic which amplified every little move/click of the mouse. Thanks for commenting this! We'll try to improve it for the next webinars.
View all posts from The Progress Team on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.