Click here to Skip to main content
Search within:



Next

Need to Create Separate DLLs for MVC 3 Controllers
Sign Up to vote bad
good
See more: C#ASP.NET
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:52
Mirza Asim Baig 414
Add a Solution

Comments
Sergey Alexandrovich Kryukov - 23 Jan '13 - 16:08
.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? —SA

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

  Print Answers RSS
Your Filters
Interested
Ignored
     
0 OriginalGriff 223
1 Ron Beyer 220
2 Aarti Meswania 200
3 Mahesh Bailwal 175
4 Rohan Leuva 170
0 Sergey Alexandrovich Kryukov 8,553
1 OriginalGriff 6,899
2 CPallini 3,648
3 Rohan Leuva 2,963
4 Maciej Los 2,308


Advertise | Privacy | Mobile
Web03 | 2.6.130516.1 | Last Updated 23 Jan 2013
Copyright © CodeProject, 1999-2013
All Rights Reserved. Terms of Use
Layout: fixed | fluid