What are the pros/cons of copying Dapper.cs into my project vs. using the dll instead vs. installing the nuget package?
This is an MVC4 project if that matters.
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 are the pros/cons of copying Dapper.cs into my project vs. using the dll instead vs. installing the nuget package?
This is an MVC4 project if that matters.
By copying in the Dapper.cs file you can directly edit your own instance of the file. This way would give you the most control over the functionality that Dapper gives you but you also run the risk of breaking it. This way also could be prone to errors with setting everything up to work correctly.
Installing the nuget package and using the dll are almost equivalent. In both cases you can access the functionality provided by Dapper.cs. This is the way the code is intended to be used. Installing the nuget package is probably your best bet because .Net automatically placing everything where it should be.