This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi Guys, When we publish our web apps, System.Data.SQLite.dll is being published as well even though we don't use this at all, and it's breaking the site when it goes up to the server. At the moment we have a post build script in place that deletes the file. But why is it appearing when we have no reference to it? Is there another way to stop it appearing in the build output? Cheers, Sean |
|
|
|
|
Are you using the ASP.NET "Publish Web Site" option? If so this is just the behaviour it takes (to pull in any indirectly referenced assemblies) and you will need to use a post build step to remove the unneeded files. We have to do this ourself for a number of our apps. Its annoying but Microsoft has no intention of changing this as they put it in to avoid people complaining that the deploy process didn't include such files when they were subsequently needed but not directly referenced.
|
|
|
|
|
Thanks for the reply Jeremy, I am using the Publish Web Site, even though I was using the post build to delete the files I didn't want, they were still being copied to the obj publish folder. In this instance the SQLite.dll has been put in to my GAC, so no matter what it was always getting pulled from there. It turned out it was actually Telerik's ORM software that stuck the SQLIte.dll in the GAC - so I uninstalled that and this problem has gone away for me now :) Cheers, Sean |
|
|
|
