Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m a bit confused.
Looking at some existing code here at my university, I see that a project is always somehow related to a single assembly. I’m new in c# and I read a bit about assemblies and modules but I didn’t find anything about the relation between the “project” logical unit and the “assembly” logical unit, and I wondered if this is a convention, and if I can somehow control this from VS.
Thanks,
Li
Yes, that’s the standard build model for Visual Studio. One project normally produces one assembly. One solution can contain more than one project. There is no direct support for creating modules, you’ll have to do that by hand so you can run csc.exe with the /target:module option. There are very few scenarios where that makes sense.