Sachin, it always helps one to get a good answer when one explains what and why?
Your what is this:
sachin.anand.pawar
I want to create separate assembly for folders in C# project.
Why?
i think this may show you the answer that you want (you can tweak this to your specific needs):
(a) for purposes of illustration, begin by building an ASP.NET MVC 4 or MVC 3 web application.
from http://www.asp.net/mvc, this video [1. Introduction],
in the "New Project" choice shows you how to create an skeleton ASP.NET MVC 3 Solution that contains one
project.
N.B.: you get one assembly for each project that you create.
(b) for any code that you want as a separate assembly, you have options like:
N.B.: if you are going to use your separate assembly in more than one project, imho, you are better off to create it as a c# class library (.dll) in a totally separate solution which you can reference from multiple locations.
B-) Please help me by completing my school survey about computer programmers on my website. Thank you!!! Gerry Lowry +1 705-429-7550 wasaga beach, ontario, canada
sachin.anand...
Member
18 Points
7 Posts
Building separate Assembly for each folder in C# Project
Jan 17, 2013 06:12 AM|LINK
Hi,
I want to create separate assembly for folders in C# project. Can anybody help me in this?
Regards,
Sachin Pawar
gerrylowry
All-Star
20513 Points
5712 Posts
Re: Building separate Assembly for each folder in C# Project
Jan 19, 2013 07:40 AM|LINK
@ sachin.anand.pawar
Sachin, it always helps one to get a good answer when one explains what and why?
Your what is this:
Why?
i think this may show you the answer that you want (you can tweak this to your specific needs):
(a) for purposes of illustration, begin by building an ASP.NET MVC 4 or MVC 3 web application.
from http://www.asp.net/mvc, this video [1. Introduction], in the "New Project" choice shows you how to create an skeleton ASP.NET MVC 3 Solution that contains one project.
N.B.: you get one assembly for each project that you create.
(b) for any code that you want as a separate assembly, you have options like:
i. same solution, separate assembly
http://msdn.microsoft.com/en-us/library/h970wzkb.aspx
"How to: Create Multi-Project Solutions"
ii. separate assembly (.dll) that you reference:
http://msdn.microsoft.com/en-us/library/wbzbtw81.aspx
"Managing Solutions, Projects, and Files"
http://msdn.microsoft.com/en-us/library/zfzh36t7.aspx
"Creating Solutions and Projects"
http://msdn.microsoft.com/en-us/library/b142f8e7.aspx
"Solution and Project Basics"
N.B.: if you are going to use your separate assembly in more than one project, imho, you are better off to create it as a c# class library (.dll) in a totally separate solution which you can reference from multiple locations.
Example: http://msdn.microsoft.com/en-us/library/ez524kew.aspx
"Managing Project References"
g.
P.S.: you may find this useful:
http://weblogs.asp.net/gerrylowry/archive/2012/11/10/clarity-is-important-both-in-question-and-in-answer.aspx