If I have uComponents v3.0.3 installed and want to upgrade to v3.1.0, all I have to do is overwrite the file at /bin/uComponents.Core.dll with the same-named file from the 3.1.0 package?
If I do this, and look in Developer -> Packages -> Installed Packages -> uComponents, my hunch tells me I would still see "3.0.3" as the package version, but perhaps this is not a big deal. Correct?
The other way I am wondering is whether I should attempt to (re-)install as a new package, which I would hope would upgrade the original one and not end up with duplicates, but I'm not sure if that's the best way. All of the documentation I've found only talks about upgrading really old versions, not relatively new/minor ones like this.
So ... my question stands: what's the recommended "best practice"?
Good question, which isn't specific to uComponents, but applies to all Umbraco packages... there isn't a "clean" way to upgrade any package.
With uComponents, all functionality is contained within the "uComponents.Core.dll" assembly. This makes it very easy to deploy/update/upgrade - as you say, literally replacing the DLL in the /bin folder.
The downside is the listings on the "Installed Packages" tree (of the Developer section) - this will display the versions that have been installed via the back-office. So if you install a newer version over an old version, then yes, you'd have duplicate entries.
The "Installed Packages" tree is actually powered by an XML config file, which you *could* manually edit... take a look at: "\App_Data\packages\installed\installedPackages.config"
My biggest advice is never uninstall uComponents to perform an upgrade... as this would delete any content/data associated with the data-types that you've used. So if you are using the back-office, then better to install a newer version over the top of an old one.
Lee, thank you very much for the concise explanation, which does all make very good sense. And not just for the great explanation, but also for the several good pointers that are very helpful. Making a quick manual update to the installedPackages.config file does seem like a great thing to do, just for neatness/completness sake.
What is best practice for upgrading?
If I have uComponents v3.0.3 installed and want to upgrade to v3.1.0, all I have to do is overwrite the file at /bin/uComponents.Core.dll with the same-named file from the 3.1.0 package?
If I do this, and look in Developer -> Packages -> Installed Packages -> uComponents, my hunch tells me I would still see "3.0.3" as the package version, but perhaps this is not a big deal. Correct?
The other way I am wondering is whether I should attempt to (re-)install as a new package, which I would hope would upgrade the original one and not end up with duplicates, but I'm not sure if that's the best way. All of the documentation I've found only talks about upgrading really old versions, not relatively new/minor ones like this.
So ... my question stands: what's the recommended "best practice"?
Thank you!!!
Hi Funka!
Good question, which isn't specific to uComponents, but applies to all Umbraco packages... there isn't a "clean" way to upgrade any package.
With uComponents, all functionality is contained within the "uComponents.Core.dll" assembly. This makes it very easy to deploy/update/upgrade - as you say, literally replacing the DLL in the /bin folder.
The downside is the listings on the "Installed Packages" tree (of the Developer section) - this will display the versions that have been installed via the back-office. So if you install a newer version over an old version, then yes, you'd have duplicate entries.
The "Installed Packages" tree is actually powered by an XML config file, which you *could* manually edit... take a look at: "\App_Data\packages\installed\installedPackages.config"
My biggest advice is never uninstall uComponents to perform an upgrade... as this would delete any content/data associated with the data-types that you've used. So if you are using the back-office, then better to install a newer version over the top of an old one.
Hope this makes sense?
Cheers, Lee.
Lee, thank you very much for the concise explanation, which does all make very good sense. And not just for the great explanation, but also for the several good pointers that are very helpful. Making a quick manual update to the installedPackages.config file does seem like a great thing to do, just for neatness/completness sake.
Thanks again!
is working on a reply...