I installed the MVC 4 beta and created a new project.
The standard template looks great now.
When you go to the nuget package manager, there are some packages that you could update.
When you update the all except Jquery UI the standard template works fine. When you also upgrade Jquery UI from 1.8.11 to 1.8.17, you get a script error on opening the default template template page.
Does someone know what is going on to solve this? I also changed the _references.js file.
Thanks
Did you make sure to update your script references in the views/shared/_layout.cshtml page? You need to update that to the proper version of the jquery/jquery UI and it should work.
The problem: jQuery.UI.Combined Version 1.8.17 - switch to 1.8.16
Related
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 am using latest version on resharper (v9 Update 1) on a asp.net mvc project in VS 2013. For some reason, resharper is not able to provide/highlight non existing actions in razor view. Previously it used to show an error and then provided a menu to generate the action (screenshot below).
I have tried repairing and reinstalling the resharper. Even devenv /resetsettings command to open Visual Studio did not help. How to get this feature back?
Either downgrade MVC packages to 5.2.2 or install Resharper EAP 9.1
See the issue https://youtrack.jetbrains.com/issue/RSRP-433112
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.
I have installed NuGet.
When I try to go to Project > Add Library Package Reference
"Add Library Package Reference" is not under the project menu. If I try to install NuGet again it says it is already installed. My application is an MVC 3 application targeting .net 4.
How can I get this option to appear?
You might also run VS as Admin (Ctrl-Shift-Click) then uninstall NuGet from the package manager dialog. Then update to NuGet 1.1 from http://nuget.codeplex.com and see if that fixes it. ASP.NET MVC is not needed.
Is it possible that some of the extensions of your Visual Studio are causing NuGet to not show the menu or crash? You could try to disable/remove them and then install NuGet from here: http://nuget.codeplex.com/
Besides, there is also a PowerShell-based Package Manager Console. You could take a look on that in case everything fails.
Make sure you have the project selected and not the solution in the solution explorer.
As of May 2012, it's now called "Manage NuGet Packages".
Especially confusing because the screenshots in the NuGet Docs have not been updated.
https://stackoverflow.com/a/9844659/24267
Normally NuGet is installed with ASP.NET MVC 3 so it should appear automatically. Try removing the NuGet package that you have installed and reinstall ASP.NET MVC 3.
Had this same issue, just realized that if you're not on the project (i.e., you have the solution highlighted in solution explorer) that the option for the Add Library Package Reference won't show. Select the project and it's there.
Whoops: Didn't notice that was already mention.
I've just had a similar problem, after trying to install a package over dial-up, which timed out.
To fix it, I renamed the registry key (so that I could rename it back if it didn't work) HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\NuGet, then restarted visual studio and opened a project. The Add Library Package Reference now works and the registry key has been recreated.
I have made a relatively simple change to the MVC 1.0 source code to correct a bug in the DropDownList HtmlHelper (discussed in another question).
I was able to rebuild the MVC solution, ran all the tests, including the one I hadd added to show the bug I was fixing, and built a new DLL.
But how do I use that?
I tried moving the new MVC dll into the project and changing all the project references to point to it, but when I try to run the MVC website, it's throwing an exception saying there's a conflict between my version of MVC and the MVC in the GAC.
I tried to use gacutil.exe to remove the one from the GAC, but it says it can't do that because it would make another program (the Microsoft Installer? fail.
What do I have to do to install my newly built version in place of the "official" version?
If you want to remove it from the GAC without uninstalling MVC (which includes the Visual Studio templates you probably need), you need to do this in the registry:
Find registry key HKEY_CLASSES_ROOT\Installer\Assemblies\Global and look for key starting with System.Web.Mvc – delete it
Now you should be able to use gacutil.exe to remove System.Web.Mvc from the GAC, and you should be able to use your version from your /bin folder.
How about changing the version number when you compile the modified MVC framework?