I have an Umbraco 7.6.1 site which I'm trying to upgrade to a later version, I'm not sure which version I'm going to yet, but the problem exists no matter the version jump.
The Umbraco project is set up in Visual Code IDE and uses NuGet.
So I go to the projects NuGet package manager and update UmbracoCMS from 7.6.1 to 7.6.2. I don't overwrite files. I've tried overwriting files and checking what it's doing in git, but with no luck either.
All seems well. I then build the project and load up the site in debugging mode. I get asked to log in and pushed to the upgrade page. I then hit continue and shown "Error during installation" instantly. It also tells me to check the logs, which are non-existent.
What am I doing wrong?
Thanks,
Dan
To fix the issue I was having I commented out any rewrite rules I was including in my main Web.config and cleared out everything in the bin folder and re-built the solution. That seemed to have done the trick.
I'm working with another developer on a project and everything has been working great until today. Now when I check out the solution to my Visual studio 2013, my reference to System.Web.Mvc is lost and I have to manually re-add it.
When I check in and she checks out, the same issue occurs for her. The path to the assembly is the same on both of our machines:
C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET MVC
4\Assemblies\System.Web.Mvc.dll
but for whatever reason, we're not in sync. As I said above, it was working great until today so something must've changed...but I have no idea what???
Any suggestions/ideas of what to look for to resolve this?
TIA
This issue occurred due to a Security update that incremented the version of MVC. So if you had References in your project pointing to the hard drive where the 2.0/ 3.0/ 4.0 version was. Your project was needing that particular version. Another way to solve this is to use Nuget to update references.
This is a post from Microsoft regarding the issue:
http://blogs.msdn.com/b/webdev/archive/2014/10/16/microsoft-asp-net-mvc-security-update-broke-my-build.aspx
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.
Upgraded from MVC Beta to MVC RC1.
Re-pointed all references in the project to point to the new assemblies
Rebooted
Everything compiles (and runs!)
But...
Opening a view (.aspx) in VS and she just disappears!
Event Viewer gives:
NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (6E075E00) (80131506)
Update 1:
Not ALL .aspx pages!
Also - it seems that writing the question on StackOverflow is the fix! grr
Update 2:
Not had the problem since posting the question but:
The only plugins I have are VisualSVN and Resharper.
I do seem to have something in the GAC for System.Web.Mvc - but it looks like the wrong version and I can't get rid of it.
I believe it must be related to some intelli-sense colouring or similar during the render of the code of the .aspx page - but now it's stopped it is hard to confirm...
Try removing all bin/obj directories, and clearing your Temporary ASP.NET Files and %TEMP% directories. Then issue the following commands from a VS2008 command prompt:
ngen /delete System.Web.Mvc
ngen /delete System.Web.Abstractions
ngen update
Also ensure that all your references (MvcContrib, anything else built against MVC) are pointing to the same version of MVC as all the others.
This seems to have worked for me (so far)
There are some framework bugs that affect all VS add-ins etc if they reference System.Core v3.5. Start by clearing out the NGen cache. "ngen update", "ngen /delete [assemblyname]" or a sweeping "ngen /delete *" usually does the trick
More details + workarounds for this (and/or similar) issues here:
http://forum.huagati.com/topic5-addin-causes-ide-to-close.aspx
http://code.msdn.microsoft.com/PowerCommands/WorkItem/View.aspx?WorkItemId=8
http://www.jetbrains.net/devnet/thread/274657
Update: finally someone from MSFT acknowledge that there is a problem:
http://blogs.msdn.com/jnak/archive/2009/02/15/potential-crash-in-vs-when-using-the-mvc-rc-on-windows-azure.aspx
Update 2: An attempt at a workaround (VS2008 add-in): http://www.huagati.com/ProjectLoader/
Update 3: Microsoft has a CLR patch (KB963676) that fixes this problem. It is not available for download from microsoft.com but it can be requested through MSFT support / PSS.
Update 4: The CLR patch is now available for download from Microsoft Connect:
https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=16827&wa=wsignin1.0
http://blogs.msdn.com/jnak/archive/2009/02/26/fix-available-asp-net-mvc-rc-crash-in-a-windows-azure-cloud-service-project.aspx
I had to remove the PowerCommands add-in to get VS working again.
I've had problems like that before. It was the webform editor. If you right-click the aspx file and choose "open with..." and select Html-editor the ide will most likely not crash on you.
Try disabling addIns one by one.
For me it was a conflict between gallio and testdriven.net I think.
Microsoft have now released a hotfix to resolve this issue.
See https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=16827&wa=wsignin1.0
Phil Haack elaborates further here - http://haacked.com/archive/2009/03/06/hotfix-for-installing-aspnetmvc.aspx
I'm having the same problem and have posted a reply on the official ASP.NET MVC forum at http://forums.asp.net/t/1378448.aspx
I'm not sure, but are you also seeing reference to the Html helpers not showing up in the views (when they don't crash)?
I don't have Gallio installed, but I do have Resharper. I'll see if disabling that helps (although that would cause me a lot of anguish).
Update: Resharper wasn't the issue, but rather the plugin "Huagati DBML/EDMX Tools." It seems some plugins might be conflicting and I encourage people to disable all plugins as a preliminary step in debugging the crashes.
I have found that any compile issues with the master page or the page itself -- even warnings -- can cause this to happen. So close the project, delete the bin and obj directories, then re-open the project. Next open your master page(s) and any other recently changed aspx/ascx files. It is important to open all before you compile.
Now, viewing each page one at a time, compile the project and resolve the warnings. Once all the warnings are resolved, close the pages and try to re-open them.
I got the exact same error. At first I thought it was the Spark View Engine add-in (because it crashed opening views) but after Christian's comment about Gallio and TestDriven.NET (I have both) I uninstalled Gallio and now it works.
The problem was indeed, powercommands for VS 2008. Uninstall them if you can live without them and the aspx pages/designers will open fine.
Actually I think my problem was some rogue copies of the Beta MVC DLLs hanging around.
I deleted them all, uninstalled the RC1 and made sure they all left the GAC and then reinstalled the RC1. So far everything seems fine.
This occurred for me after setting the reference to System.Web.Mvc to Copy Local = True. This placed the System.Web.Mvc.dll file in my bin folder.
The next time I opened any aspx pages Visual Studio crashed. Changing the dll in the bin to System.Web.Mvc.dll.bak fixed the problem.
I finally (after a fews days of trying everything) got it resolved by uninstalling the Spark View Engine add-in, which crashed when opening .aspx and .js files!
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>