I was wondering if someone could explain the differences between the Umbraco Cms Core Binaries Package and Umbraco Cms NuGet Package?
A good question. First I would recommend the Umbraco community site for questions and answers over at http://our.umbraco.org
The main Umbraco.Cms NuGet package includes the main Umbraco CMS for it to run and has a dependendcy on the Umbraco.Cms.Core Binaries Nuget package for it to work.
If you were to build a custom extenion or package for Umbraco, you may not need the main CMS but just the need that DLLs that ship with Umbraco so you can develop against the API.
I hope this helps.
Thanks,
Warren :)
Related
What is the difference between umbraco and vanila umbraco.
i'm currently using umbraco 6.2.1 version in my website.
Any special procedure available for upgrading this version to Vanila umbraco version.
Vanilla Umbraco means a fresh clean installation of Umbraco, without any customization.
Vanilla is a general term used for software, see also on wiki
Related to upgrading, one approach is to do a new installation of Umbraco (we can called it a vanilla installation) and then deploy your code, and migrate the content. Instead of the General Umbraco upgrade instructions.
I'd say that there is no running website with a vanilla Umbraco install. Umbraco is not a typical CMS. You are customizing it as soon as you start setting up your site in it. This is partly due to a choice on the Umbraco HQ team's decision to store their settings in the same files where you change settings by using Umbraco, requiring you to merge certain files during the upgrade.
As for upgrading, I'll warn you, there are a few ways to install Umbraco (Web PI, Nuget, Zip file), and if you upgrade in a way different than you installed, it can be hell. Step one, back up your site (front-end file-system files and db)! If you did not install Umbraco via Nuget (in Visual Studio), do not upgrade via Nuget. You will regret it.
Umbraco upgrades are a problem.
If the versions are minor running the update-package umbracocms nuget might work, but it often leaves the project mismatching version assemblies elsewhere.
Upgrading Umbraco is a bit of a minefield. Soz
Umbraco is now at version 11 and have moved their code base from the .NET framework into .NET core. Newer version is offering so much more, block-list, block-grid, inline editing, so many new and improved property editors. Editing experience and working with the CMS has changed so much since version 6.
Vanilla Umbraco would a term for a non-configured, fresh install.
You can find out everything you need to know about Umbraco on their documentation pages.
https://docs.umbraco.com/getting-started
Umbraco is a free open source project so there is no cost if you want to roll your sleeves, dig in and move over to the newest version. There are some paid offerings as well that would give support if you needed it.
Now that they have moved away from the .NET framework and moved their code base over to .NET Core there is no longer a direct path to upgrade from version 8 and earlier to the most recent version 11.
I would recommend you set up a fresh install, configure and customize as desired and then move any relevant content over to your new site.
There are many articles out there detailing how others moved over to the newer version.
Good article here on how they upgraded from version 7 to the newer version 11.
https://skrift.io/issues/how-i-upgraded-my-umbraco-v7-project-to-umbraco-v11/
Worth the read if your planning on going down that path.
Good luck.
So I have Umbraco v6 currently setup via a release download and split into a class library and a website. I need to upgrade to v7 at some point and have some question on how I should setup.
What are the pros/cons of setting up through Nuget vs Downloading source and creating project?
Devin
The pro of using nuget is that you don't have to build the project from scratch. If you have a need and/or desire to understand how umbraco is built, by all means pull down the source code, but if you just want to use umbraco, and customized it thru the hooks it provides, then the nuget packages will be easier.
I've done both (though not with the latest version), and using nuget is far easier and quicker to get going.
I want to try out NoSql Database, and based on some articles RavenDb is highly recommended for .Net. Now I cant even start because I cant install RavenDb.Database (v3.0.30000) on my Web project. Im not sure if the issue is in Nuget.
Im using the below tools if it matters.
.Net 4.5.2
ASP MVC 5 (empty template/no package added yet)
Visual Studio 2015
Yes, this is a nuget issue.
can you try this using the command line client?
Alternatively, just download the ravendb zip from our site
https://www.nuget.org/packages/RavenDB.Client/3.0.30000
find your version and download it from the menu on the left, hope this will be fixed
Related to: Package an ASP.NET MVC application with Nuget
I'm trying to get a mode where I can edit an MVC project and package it easily.
As often suggested it is wise to replace a namespace using NuGet pre-processor functionality.
This would mean that I would have to edit my source files and add the pp extensions to each pre-processed source file.
Are there any tips and tricks to make this less labourious?
There is such a tool, that did almost exactly what I wanted. It's on Codeplex so I could participate in the development, yay!
https://nugetpackager.codeplex.com/
It has a common-line interface too, so I can script my updates.
Okay, so help me understand something here. I've got a new MVC solution and want to use NuGet to keep Modernizr up to date.
The problem is, NuGet puts the Modernizr scripts under ~/Scripts. This won't work--we've decided to put our JS in ~/js.
How do I modify the configuration of this package to tell NuGet that the Modernizr package should go in ~/Scripts or ~/Scripts/global instead?
I don't think you can do this - I don't think this is functionality of NuGet, but rather the location of the scripts inside the NuGet package. This could vary from one package to another :-(
This is currently not a feature of NuGet, but it was mentioned in discussion on the a NuGet forums including members of the NuGet team. I don't see any work item that has officially been created for this yet, unfortunately. I performed a quick search of the NuGet issues list for the word "location" and didn't see one out there for this. You might want to request it as a feature.