I want to adjust my MVC project, so that I can build a multi-file assembly. My intent, as a proof of concept, is to make the root web.config a part of the MVC assembly. The rationale for doing so, would be to prevent tampering with the web.config file.
The presumed "I must modify" section of the MVC project is here:
<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" /> <Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets" /> <Target Name="MvcBuildViews" AfterTargets="AfterBuild" Condition="'$(MvcBuildViews)'=='true'"> <AspNetCompiler VirtualPath="temp" PhysicalPath="$(WebProjectOutputDir)" /> </Target>
I don't recall how I can "influence" the imports. For example, is there a property I can set to make the
csc build step produce modules instead of assemblies? And even if I achieved that, I need a list (viz. itemGroup) of the resulting module(s), so that I can feed that into the linker (either "csc /out" or "al /out /target").
Anyone done this before? Pointers?