What is the difference between Assembly and a DLL? While sending the code to a remote client, should a DLL file be sent or should a Assembly be sent (When direct TCP connection is available between two)?
Share
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.
What is the difference between Assembly and a DLL? While sending the code to a remote client, should a DLL file be sent or should a Assembly be sent (When direct TCP connection is available between two)?
An assembly is .NET’s ‘minimum unit of deployment’. Usually an assembly corresponds to a single file, but it doesn’t have to – you can have multiple files, with one of them being the master which knows where all the other bits are.
Single-file assemblies are usually DLLs or EXE files. If you’ve got a normal class library and you just want to send it to the other side, the DLL is what you want. I’d only worry about more complicated scenarios as and when you run into them 🙂