After NuGet get into VS2013, do we need the NuGet files anymore?
I installed Umbraco via NuGet to Visual Visual Studio 2013. Is there anything Umbraco is relying on if I get rid of the NuGet packages?
I am asking because, we multiple developers and we are using TortoiseSVN as our repo. We ran into issues with the NuGet stuff with multiple Developers.
If we don't plan on upgrading our Umbraco instance versions through NuGet but through the manual process, do we really need the NuGet stuff anymore in our solution?
I think that should be a matter of making sure that the nuget stuff is simply ignored so it's not being pushed to the repository?
When using a system like git then it's recommended to ignore these visual studio and Umbraco files https://www.gitignore.io/api/visualstudio,umbraco - This is a generated list from gitignore.io so read through it with caution since you may not want to ignore it all but just some of it depending on your needs.
After NuGet get into VS2013, do we need the NuGet files anymore?
I installed Umbraco via NuGet to Visual Visual Studio 2013. Is there anything Umbraco is relying on if I get rid of the NuGet packages?
I am asking because, we multiple developers and we are using TortoiseSVN as our repo. We ran into issues with the NuGet stuff with multiple Developers.
If we don't plan on upgrading our Umbraco instance versions through NuGet but through the manual process, do we really need the NuGet stuff anymore in our solution?
Thank,
Carlos
Hi Carlos
I think that should be a matter of making sure that the nuget stuff is simply ignored so it's not being pushed to the repository?
When using a system like git then it's recommended to ignore these visual studio and Umbraco files https://www.gitignore.io/api/visualstudio,umbraco - This is a generated list from gitignore.io so read through it with caution since you may not want to ignore it all but just some of it depending on your needs.
Hope this helps.
/Jan
@Jan,
That is exactly what I needs. This helps out a lot.
Thanks,
Carlos
is working on a reply...