I have a source controlled Umbraco project in Visual Studio / TFS that I publish on changes/updates from withing Visual Studio to the dev and stage environments.
That works well, but I don't know the correct path for updating packages (from package repository) in that scenario.
Actually I update packages by adding them in the backend (ZIP upload), adding new files to the project/source control (manually) and publish the changes (inlcuding installedPackages.config) to the servers.
That seems to work, but is it a solid way to handle that? Or should I upload the packages inside each backend (dev, productive) manually without using the Visual Studio publish function?
Using the "Publish" way, it seems that the version info in the backend (Installed packages) isn't up-to-date on all environments. Is that a problem?
Update packages - Visual Studio/Publish
Hi,
I have a source controlled Umbraco project in Visual Studio / TFS that I publish on changes/updates from withing Visual Studio to the dev and stage environments.
That works well, but I don't know the correct path for updating packages (from package repository) in that scenario.
Actually I update packages by adding them in the backend (ZIP upload), adding new files to the project/source control (manually) and publish the changes (inlcuding installedPackages.config) to the servers. That seems to work, but is it a solid way to handle that? Or should I upload the packages inside each backend (dev, productive) manually without using the Visual Studio publish function?
Using the "Publish" way, it seems that the version info in the backend (Installed packages) isn't up-to-date on all environments. Is that a problem?
Best Regards Andreas
is working on a reply...