I'm looking for some advice in regards to using Umbraco with version control. I have been using Umbraco for just over 2 years and this is the biggest headache that it gives me and the small team I work with.
We tend to do an install manually setting up in IIS. We then have one person build out the project and commit the files to SVN. If that person is off or gets pulled onto another project and someone else takes over when they checkout the files and begin working with them in VS 2017 we start to have a massive tug of war with packages having to be uninstalled and reinstalled. This can take up a good hour or two of development time.
Does anyone else have this issue, is it something we must be doing wrong? Our background is more WP and MEAN stack but we love using Umbraco when it fits the project we just need to Iron out these issues.
I would advice you to go over your ignore rules. I use GIT and not SVN but I imagine its not that different.
I usually ignore every NuGet package (packages folder + bin folder) and run the "restore nuget packages for this solution" option. I need to ignore the bin folder for this to work properly.
For packages in "App_Plugins" I include them all.
Here is some of my .gitignore file, I hope it helps.
#Ignore unimportant folders generated by Umbraco
**/App_Data/ClientDependency/
**/App_Data/ExamineIndexes/
**/App_Data/Logs/
**/App_Data/[Pp]review/
**/App_Data/TEMP/
**/App_Data/cache/
**/App_Data/imgcache/
Cached/
# Ignore Umbraco content cache file
**/App_Data/umbraco.config
# Don't ignore Umbraco packages (VisualStudio.gitignore mistakes this for a NuGet packages folder)
# Make sure to include details from VisualStudio.gitignore BEFORE this
!**/App_Data/[Pp]ackages/
!**/[Uu]mbraco/[Dd]eveloper/[Pp]ackages
# Visual Studio temp something
.vs/
# NuGet Packages
*.nupkg
# The packages folder can be ignored because of Package Restore
**/packages/*
# except build/, which is used as an MSBuild target.
!**/packages/build/
# Visual Studio
[Dd]ebug/
[Bb]uild/
[Rr]elease/
[Oo]bj/
[Bb]in/
*.aps
*.bak
*.build.csdef
*.cache
*.ilk
*.lib
*.log
*.meta
*.ncb
*.obj
*.pch
*.pdb
*.pgc
*.pgd
*.rsp
*.sbr
*.scc
*.sln.docstates
*.suo
*.tlb
*.tlh
*.tli
*.tmp
*.user
*.vspscc
*.[Pp]ublish.xml
*_i.c
*_p.c
.builds
# Umbraco
**/Umbraco.Site/aspnet_client/
**/Umbraco.Site/media/
**/Umbraco.Site/imagecache/
Umbraco.Site/scripts/
Umbraco.Site/css/
node_modules/
Umbraco.Frontend/node_modules/
Umbraco.Frontend/bower_components/
.vscode/
.vs/
.git/
Issues with Umbraco and version control
Hi,
I'm looking for some advice in regards to using Umbraco with version control. I have been using Umbraco for just over 2 years and this is the biggest headache that it gives me and the small team I work with.
We tend to do an install manually setting up in IIS. We then have one person build out the project and commit the files to SVN. If that person is off or gets pulled onto another project and someone else takes over when they checkout the files and begin working with them in VS 2017 we start to have a massive tug of war with packages having to be uninstalled and reinstalled. This can take up a good hour or two of development time.
Does anyone else have this issue, is it something we must be doing wrong? Our background is more WP and MEAN stack but we love using Umbraco when it fits the project we just need to Iron out these issues.
Thank you
I would advice you to go over your ignore rules. I use GIT and not SVN but I imagine its not that different.
I usually ignore every NuGet package (packages folder + bin folder) and run the "restore nuget packages for this solution" option. I need to ignore the bin folder for this to work properly.
For packages in "App_Plugins" I include them all.
Here is some of my .gitignore file, I hope it helps.
Thank you I will have a look at this, I'm trying to push using GIT instead so this might help add some weight to this.
is working on a reply...