C # web project, where do all dependencies come from?
The strangest thing happened today with my ASP.NET MVC project. Today I built an installer project and all of a sudden all these new dependencies appeared! Ugh.
Microsoft.SqlServer.BatchParser.dll
Microsoft.SqlServer.ConnectionInfo.dll
Microsoft.SqlServer.Dmf.dll
Microsoft.SqlServer.Management.Sdk.Sfc.dll
Microsoft.SqlServer.ServiceBrokerEnum.dll
Microsoft.SqlServer.Smo.dll
Microsoft.SqlServer.SqlClrProvider.dll
Microsoft.SqlServer.SqlEnum.dll
Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll
Microsoft.VisualStudio.TeamSystem.Data.dll
Microsoft.VisualStudio.TeamSystem.Data.UnitTesting.dll
Microsoft.Web.Mvc.dll
This is in addition to the normal dependencies (I want them) ...
Microsoft.Web.Mvc.dll
System.Web.Abstractions.dll
System.Web.Mvc.dll
System.Web.Routing.dll
Any idea what I could do to show these new dependencies.
source to share
Ok, here we go:
Microsoft.Web.Mvc.dll is for experimental MVC framework features that probably won't make it to the final release
Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll, Microsoft.VisualStudio.TeamSystem.Data.dll, Microsoft.VisualStudio.TeamSystem.Data.UnitTesting.dll probably exists because you chose to include Unit Tests in your project when you created it.
Microsoft.SqlServer. *. dll probably exists because you used the attached database file or LINQ to SQL classes (I'm assuming you have data access for your models, right?) This is rather strange since they are usually not needed to access data ...
If you don't need these dependencies, you can try to exclude them from your deployment project one by one until something breaks (right click on the dependencies in the solution explorer and select Exclude Dependency). Sometimes the VS Deployment Tools overdo it a little with dependency checking.
source to share