How do I find out what references what with the DLLs from 3rd party (and MS)?
I have an AspnetMvc 4 project and see a DLLs named *Oauth* and DotnetOpenAuth*.
Now I'd like to get rid of unnecessary load and my project is anonymous so I thought it would be a good idea to delete said DLLs and references.
So I delete through Nuget
UnInstall-Package Microsoft.AspNet.WebPages.OAuth
But to no avail. I delete the files and update packages.config to realise something needs them. But how do I find out what? My stuff is not the culprit afaik.
Here you can follow this tutorial step by step to create a webform ( same you can do in MVC ) also codes are available in GitHub. Here is the link :
It looks like you pulled in the security portion of the mvc4 application. If you do not use the library(s) then you can discard them.
The main packages for MVC are
Microsoft.AspNet.Mvc
Microsoft.AspNet.Razor
Microsoft.AspNet.WebPages
Microsoft.Web.Infrastructure
I don't think the above packages will pull in the oauth portions.
Related
I installed this NuGet package through the Package Manager Console. It messed up my project and since System.Net.Http is missing so it is impossible to build my ASP MVC WebApi project anymore.
I tried removing references to System.Web.Http.WebHost.dll from the project and adding the previous one (that used to work) and regardless of which I used now, the Http part of the namespace can't be found.
Have you ever had this problem ? I read trashing the project and starting from scratch solved it for others, but that's not really a solution in my book.
Any ideas ?
Try to run this in Package Manager Console:
Update-Package Microsoft.AspNet.WebApi.Cors -Reinstall
If you get any errors, comment below.
I trashed the project and restarted a new one (Web API). I'm just drag and dropping class files back in the new one.
It wasn't under source control. That'll teach me.
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.
Following the documentation described in this link, I'm trying to install the Breeze with NHibernate support.
But the Breeze.Server.ContextProvider.NH does not exist, what should I do? What are the steps to use Breeze with NHibernate?
The Breeze.ContextProvider.NH source and dll is available on GitHub, but we are still in testing on it, so we haven't created a nuget package for it yet.
The nuget package is now available, and the NorthBreeze sample
is now updated to use Breeze 1.4.8 and WebApi 2
I updated the sample by removing all the existing references, then installing the nuget package Breeze.WebApi2.NH
Except for some using statements, and one redundant line of the Web.config, I didn't need to change any code.
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?
Unfortunately, my company's IT policy doesn't allow me admin privileges to my own machine. However, I want to start working ASP.Net MVC; but the installer won't install the framework w/o admin rights. Is there anyway I can install MVC manually; like copying relevant DLLs somewhere, etc. Any constructive advice is greatly appreciated.
You can download & compile ASP.NET MVC yourself - and either include it as a referenced project, or just grab the resulting binaries and add them to your project like any other DLL.
Look for the link to MVCBetaSource.zip on this page - it's a pretty straightforward build using Visual Studio, and (if I recall correctly) includes the few binaries (System.Web.Abstractions and System.Web.Routing) that aren't part of the MVC source itself.
As of preview 3 or 4, ASP.Net MVC became binnable. What I've done in my solutions is have a 'binary references' folder at the root of the solution and make references to those local files in each project that needs them. You should copy:
System.Web.Abstractions.dll
System.Web.Mvc.dll
System.Web.Routing.dll
Once done, refer to these assemblies and things should work just fine. The biggest hurdle you face is extracting them from the MSI.
MVC is bin deployable, so if .Net 3.5 is installed with SP1 you should be good. Just make sure you mvc dll gets put in your bin folder and deploys out. The tricky part is the wildcard in IIS6, IIS7 will do this automatically but for 6 you need to make a rule, good luck.