Actually i was trying to build MVC project on Visual Studio 2019 but when i'm switching to visual studio 2019 so i get some reference error so finally i resolve all the issues then build solution so i have one error on Telerik.Web.UI reference. I'm already spend 2 hours on this issue but still i don't have an idea about it please help.
'Could not load file or assembly 'Telerik.Web.UI, Version=2015.1.225.45,
Culture=neutral, PublicKeyToken=121fae78165ba3d4' or one of its dependencies. Operation is not
supported
Solved, problem is that i have telerik license file so delete this license file and add reference then build project, its working.
I am glad you've managed to solve the problem.
For anyone else who is experiencing this issue in the future, let he/she checks the following KB article: https://www.telerik.com/support/kb/aspnet-ajax/details/how-to-fix-license-file-related-errors
My project was working in visual studio 2012 MVC4 i opened it in visual studio 2017 and i see under URL,model,View Bag,im getting error stating model does not exist,Url does not exist in the current context,
i dont know what im missing something which i have to add when i want to open project in visual studio 2017,in webconfig my mvc version :
System.Web.Mvc, Version=3.0.0.0
i changed it to 4 also but still the same errors,what could be the cause?am i missing a reference?
Are you able to run the project, even though it's giving you errors? I had the same issue when I started using VS2017 with an older project. For some reason, it could not resolve the dependencies and restore packages was not working. However, I am now on VS2017 15.8.6, and a simple "Rebuild Solution" did the trick. Failing that, you can try some of the suggestions mentioned here. Good luck, I hope it helps!
I'm using VS 2008 with SP1, on WinXP Pro, and I successfully installed the MVC package from Microsoft. I start a new project, select the MVC web project type, and give it a name and folder. When I press go it hangs forever.
The "ProjectName" folder is created, but nothing else is there.
I can create and open all my other projects without any issues.
Any ideas what's causing this issue? I can't try the MVC framework if I can't create a project!
If you use Process Monitor & Process Explorer, you can probably find out what VS is waiting for.
PM: http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
PE: http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
I had a similar issue: Instead of uninstalling Visual Studio add-ons I tried the fix.
I found this blog post form the VS team:
http://blogs.msdn.com/webdevtools/archive/2009/03/03/hotfix-available-for-asp-net-mvc-crashes-with-azure-power-commands-resharper.aspx
that points to a fix:
https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=16827&wa=wsignin1.0
It Worked!
Give a try to ASP.NET MVC 2 Preview 2.
After installing ASP.net MVC, when I attempt to load a existing or a new MVC application (straight from New Project - A project for creating an application using the ASP.NET MVC framework (1.0) (.NET Framework 3.5)) I get the following error:
Microsoft Visual Studio
The project file 'path' cannot be opened.
The project type is not supported by this installation.
OK Help
Tried reinstalling which didn't help. Tried devenv /setup which also didn't help.
Any ideas?
The reason was because I didn't have the Visual Web Development part of VS installed. I only had the C# language. As such, MVC didn't check and installed successfully but couldn't use the underlying part.
After installing the Web Dev bit everything worked as expected...
You could also try to run the following command:
devenv /ResetSkipPkgs
This will try to load any Visual Studio packages that failed previously at some point, such as the WPF project flavor package, which would cause the error message you're seeing.
Not sure if this is the same issue but going through the uninstall and re-install of beta and RC versions and finally the RTW I ended up with two ASP.NET MVC Web Application icons in my "File/New/Project" dialog.
If I click the first link, my project does not load correctly. But if I click the second one everythign works great.
I haven't dug into the templates folder to see if there is a remnant from a previous version or what.
Brian
Did you install SP1 for .Net and VS2008?
The way I corrected this issue of not being able to open a ASP.NET MVC 1.0 for myself goes like this when I was using VS 2008
Install SP1 for VS 2008
Install MVC 2.0 framework
I realized I had an MVC 1.0 project and I used this tool to change the project to MVC 2.0.
The tool works great, props to Eilon Lipton never met the guy but I'm down with anyone that will make my life easier.
http://weblogs.asp.net/leftslipper/archive/2009/10/19/migrating-asp-net-mvc-1-0-applications-to-asp-net-mvc-2.aspx
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>