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.
I had a Visual Studio 2012 project that I imported into Visual Studio 2013. I upgraded Entity Framework to version 6. I got the following error when I started the first time: Unable to cast object of type 'Glimpse.Ado.AlternateType.GlimpseDbConnection' to type 'System.Data.SqlClient.SqlConnection'. Since this was a prototype app, I wasn't concerned about Glimpse, so I uninstalled it via NuGet, which removed the error and I carried on.
Now, I'm deploying to Azure websites and I keep getting that error!
Glimpse is uninstalled.
It works fine in release and debug locally.
I tried putting System.Data.Metadata.Edm.MetadataWorkspace.ClearCache(); in the Application_Start like this says. (Even though I don't run queries in Application_Start
I suspect I have a caching problem on Azure, but I'm not sure. How do I get the Azure deployment to remove Glimpse like the local install has?
Update: "Fixed"it by deleting the azure website and recreating it. Would still love to hear how to do with this without going with the nuclear option.
This is a bug and is fixed in the release that will hopefully be going out tomorrow - see here for more details https://github.com/Glimpse/Glimpse/issues/540.
I also faced this error and later on found the resolution.
Issue was that I had MVC5 and EF6 based solution and i had imported Glimpse.mvc4 and Glimpse.ef5 packages and they were incompatible i think .
Once i upgraded to Glimpse.EF6 and Glimpse.MVC5 it started working fine.
also had the same one, when I opted to remove Glimpse.
you can prevent this by deleting the bin/ and obj/ folders from your project folder(s) as Glimpse is copied to your bin during debugging.
I have gone here on CodePlex and downloaded nopCommerce v2.60. I am on a Windows 8 Pro 64x Machine, I have .NET Framework and SQLEXPRESS 2012 installed.
The nopCommerce solution installs perfectly fine, no problem ! All front-end stuff work fine. But when I try and access:
localhost:xxxx/admin
I get the following error:
I have already tried re-installing with fresh database and files, but no success. I don't know how to get it to work. Before this use to work no problems at all!
You need to BUILD the whole solution before running. :)
Ok after an exchange of emails with a friend of mine who is really good at C# and has excellent experience with nopCommerce. He too was able to duplicate the problem on his machine running Win 8 Pro 64x along with VS 2012, like me.
It turned out, for some strange reason, one must build, and re-build the solution a couple of times before running it in VS 2012.
So open up your nopCommerce fresh in VS2012, and before you run it, re-build the solution 2 or 3 times, and then run it.
That was the fix for me. So annoying that I spent so much time stuck with it, but I'm glad it works now.
Recently I have been working on a website using a trial version of DevExpress with the latest version of Entity Framework, but my trial has run out. Is there a free alternative anyone knows of that I could use in it's place? I'd like to keep the whole MVC flow going.
DevExpress only provides extensions for (and not the root of) MVC. As long as you can go without the extended versions of the charts, tables and other controls you'll be fine. Otherwise, if you're that dead-set on their controls or have a lot invested you may look at just purchasing the package.
Also, to be clear, EF is a freely-available library (if you have NuGet it's very easy to obtain) so anything relying on that is safe:
Install-Package Entity-Framework -Version 5.0.0
That would install the latest solid build to your project.
I have installed VS 2008 SP1 on W2k3 OS. After I installed ASP.NET MVC beta and tried creating ASP.NET MVC type project I get the following error.
"the project type is not supported by this installation"
Let me know if you have fixed this issue.
I tried some of the solutions posted here but still no joy. Finally I replaced the ProjectTypeGuids to this one below in the project file and it loaded fine
<ProjectTypeGuids>{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
I came across something while having issues of my own.
In short, try:
Run the Visual Studio Command Prompt as Admin.
Execute:
devenv /setup
It then whirs away for a bit (VS2008 will not open), once the prompt returns fire up VS and all (may) be back to normal.
I came across this when my MVC projects got messed up when trying to get the Entity Framework up and running :)
The problem is that MVC 2 is not completely backward compatible. Visual Studio cannot open MVC 1 apps without MVC 1 installed. So if you just install MVC 1, which can install together with MVC 2 you should be just fine.
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=53289097-73ce-43bf-b6a6-35e00103cb4b
I had the same problem with MVC v1. Turns out that I hadn't installed the "Visual Web Developer" feature.
This SO user had the same issue.
My situation was slightly different: I was trying to open an existing MVC 3 project. Turns out I didn't have MVC 3, installing it from here fixed the problem for me.
i installed visual web developer from the Visual studio 2008 installation dvd and that fixed the problem
Tried to install ASP.NET MVC 1.0. It works to me.
ewalshe - same thing worked for me. I know this is an old post, just wanted to put this out there for anybody else. I had an existing solution in source control (Vault), and wanted to set up my home computer for development. I installed Visual Studio 2008 at home without the following options:
C++
Visual Basic
Visual Web Developer
When I pulled down the solution from source control, all projects loaded EXCEPT my web project - VS simply did not recognize it. A fresh installation using the default options and a restart fixed my problem. I do not have the time nor the desire to really figure out which of the above is necessary for Web Application projects to work... maybe somebody will chime in.
~ryan
I was getting the same error and found this question in a Google search for the answer. Most answers unearthed in the search suggested that old project types were being moved onto a machine with a different version of Visual Studio installed. None of which applied to me.
I've got VS2008 installed on a machine (running 64bit Vista) at work and recently installed the ASP.NET MVC beta, without any problems.
I wanted to replicate my work environment on my Mac, so I installed VS2008 with the ASP.NET MVC beta into a WinXp installation running within a Parallels VM. When I went to create a project with the ASP.NET MVC Web Application template I got the "the project type is not supported by this installation" error.
I finally got things working by yet another reinstall of VS2008 (a clean install, not a repair). This time I choose the default installation options, rather than customising things as I usually do. I normally deselect VB, the mobile device, office and other non C# development stuff - I don't have much free space on my Mac.
After the clean install of VS2008 I did a windows update, installed VS2008 SP1 and finally installed the ASP.NET MVC beta.
It seems that when I customised the VS2008 install, I deselected something essential for the correct operation of the MVC beta. I don't have clue what that something is, I'm just happy that after three days I can play the the MVC stuff at home.
Its been a month since you posted the question. Have you made any progress since?
This is sometimes caused by running a version of Visual Studio which doesn't support MSTest.
This might be obvious, but it fixed it for me. I had installed ASP.NET MVC prior to installing Visual Studio 2008. Once I removed MVC and reinstalled, I no longer had the problem.
install ASP.NET MVC 1.0. It works to me.
In Windows 7 if you are not running as the local "Administrator" and have UAC turned on the install will silently fail. The solution is to disable UAC, reboot, and the install should succeed.
I kept running into this problem. Running devenv /setup and devenv /resetskippkgs did not work for me. Nor did removing project guids. I installed MVC 1.0 and it still didnt work. Then I installed MVC 2.0 and that seemed to do it.
I had MVC 2 installed on my machine and I was still getting this error message. I installed MVC 1, no GO. i installed web Developer No GO. I finally uninstalled MVC1 and MVC2 and then reinstalled MVC2: http://www.microsoft.com/Downloads/en/details.aspx?familyid=C9BA1FE1-3BA8-439A-9E21-DEF90A8615A9&displaylang=en
The re installation of MVC 2 solved the problem for me. Hope this helps someone else.
Thanks
If you are trying to run an MVC application, try running AspNetMVC1.msi. It worked for me, so hopefully it will resolve your problem.
VS2008; ASP.NET MVC 2 on 64-bit machine receiving the issue:
"the project type is not supported by this installation"
Solution: Thanks to Bert Huijben from above. Under the VS install in the start menu, in the VS Tool folder, ran VS2008 x64 Cmd Prompt. Executed commands:
devenv /setup
...still project errored and didn't open, then ran
devenv.exe /resetskippkgs
... and then success!
I had to rebuild my development VM to solve this one. Clean install FTW.
Tried #ryan and #Rob Cooper answers with no joy. Running this in a vhd on Win7.
Zoned in on Mvc and that's where problem lies. Not 100% but think issue is that I was trying to open a project that didn't have latest Mvc release, which new build had.
Temporary solution is to rollback to previous version of Mvc. Then when that's happy, upgrade project to latest Mvc and then machine.
Ran into this problem when I had VS2008 running by accident when I started the ASP.NET MVC install. Closed VS, uninstalled ASP.NET MVC, then reinstalled it and everything worked fine.
Vivek Ayer's solution also worked for MbUnit projects. Additionally, simply deleting the first GUID (rather than replacing it with "{349c5851-65df-11da-9384-00065b846f21}") worked.
If you are running Visual Studio 2010 and want to open/create MVC 3 solutions you have to have the Visual Web Developer component of Visual Studio installed.
If you have done a default installation without customization then this component is installed.
If you do a customized installation and say thought you only wanted C# stuff installed you may have unchecked the Visual Web Developer component thinking you didn't need it. You need it for any MVC development. Simply re-run your VS setup and make sure this component is selected.
The MVC 3 download and installation will work properly even without this component installed. However, you will not be able to open or create a MVC 3 solution.
The trick to getting around this problem is the ProjectTypeGUID, but the GUIDS listed elsewhere in this and other posts didn't work for me.
In the end (and this is my suggestion), I created a new MVC project, then open the *.vbProj file and copy out the ProjectTypeGUIDs I found there. When I transposed those into the vbproj file of the project I was having trouble with, everything started working.
In my case (for an existing VS10 VB project), the right GUIDs were:
<ProjectTypeGuids>{F85E285D-A4E0-4152-9332-AB1D724D3325};{349c5851-65df-11da-9384-00065b846f21};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}</ProjectTypeGuids>