<p>When you grab the source and make a change and try to build, it is a PITA. I don't have all of the appropriate SQL client tools installed, so I was unable to actually run the makeinstall.cmd successfully. I had to go in and strip out all of the versions of SQL that I didn't need, then fix all of the references. It was a pain.</p>
<p> </p>
<p>Or, if you are unable to distribute the DLLs, then can some instructions be added to tell end users how to easily download and install the appropriate files and make it easier for them to do a build.</p>
<p> </p>
<p>It is a great tool when you only have to install the MSI :)</p>
Comments: ** Comment from web user: kevinidzi **
<p> </p>
<p>Or, if you are unable to distribute the DLLs, then can some instructions be added to tell end users how to easily download and install the appropriate files and make it easier for them to do a build.</p>
<p> </p>
<p>It is a great tool when you only have to install the MSI :)</p>
Comments: ** Comment from web user: kevinidzi **
I'm glad you were able to run the makeinstall - sorry it was a pain. I must say, I did make it more for my own ease of deployment :) since I have 3 versions to support at once. I can work on some sort of doc perhaps to make it easier to build. Unfortunately, the installer sort of relies on there being all three versions (sql2005/2008r2/2012) - but perhaps I can find a way to break it out. I made this into a task for me to do sometime.