Click here to Skip to main content
13,140,231 members (47,605 online)
Rate this:
Please Sign up or sign in to vote.
See more:
when publishing my MVC3 razor project it create single DLL for my whole project.
I need to have separate DLLs for every controller in my Project.So that whenever I want to change any Controller code, I would deploy only that DLL.
Posted 23-Jan-13 4:52am
Sergey Alexandrovich Kryukov 23-Jan-13 16:08pm
.NET functional units are not "DLLs", they are assemblies and modules. "DLL" is nothing but naming convention. It could be anything, even EXE. Start from there. I see no problem. If you don't know how to create and reference assemblies, you are not doing .NET development at all and need to learn it. Need help? Yes, you can deploy a part of solution, only one assembly (not DLL, assembly, but the file may or may not be DLL), with care. It's the best to have well-controller versioning policy and version checks. Any problems with that?

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy |
Web01 | 2.8.170915.1 | Last Updated 23 Jan 2013
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100