tag:support.appharbor.com,2010-11-23:/discussions/problems/427-missing-referenceAppHarbor: Discussion 2011-07-28T22:40:52Ztag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T05:43:44Z2011-04-16T05:43:44ZMissing Reference<div><p>Are you sure the dll is also pushed to AppHarbor?</p></div>friismtag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T05:46:32Z2011-07-28T22:40:51ZMissing Reference<div><p>Well, I'm sure that git is adding it because I removed it and
re-added it just to see the message and it's there. And I'm sure
it's physically in the directory. Whether or not it made it to AH,
I don't know. Is there a way to verify that?</p></div>donniefitz2tag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T05:59:52Z2011-04-16T05:59:52ZMissing Reference<div><p>Could you add <a href=
"mailto:support@appharbor.com">support@appharbor.com</a> as a
collaborator, and we'll take a look.</p></div>friismtag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T06:02:21Z2011-07-28T22:40:51ZMissing Reference<div><p>Sorry, I'm not sure what you mean. Add **@appharbor.com to the
project? How is that done? Thanks for the quick replies by the
way.</p></div>donniefitz2tag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T06:04:27Z2011-07-28T22:40:51ZMissing Reference<div><p>Okay. Got it. I added support@appharbor to the project.</p></div>donniefitz2tag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T06:05:07Z2011-07-28T22:40:51ZMissing Reference<div><p>that is "support"</p></div>donniefitz2tag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T06:40:44Z2011-04-16T06:40:44ZMissing Reference<div><p>Hi Don,</p>
<p>The problem occurs because Microsoft.Practices.Unity is
referenced in different ways around the project - and sometimes it
doesn't reference the dll. Make sure every reference in all the
projects points to the Microsoft.Practices.Unity dll - as it is
used several places it might make sense to put it in the
"Dependencies" folder.</p>
<p>I would also recommend you to remove all the obj/debug folders
from the git repository. The reason is that they're not necessary
for us to build the code and it might lead to confusion as to why
it doesn't build on AppHarbor or an continous integration
server.</p>
<p>In this case you're not experiencing any build errors locally
because the Microsoft.Practises.Unity file is actually already in
the obj/debug repository (and the reference doesn't explicitly
point to the dll). We build your code under the release
configuration and there the dll is missing.</p>
<p>An extra bonus is that your commits will only contain the
relevant code change and git won't track all the binaries causing
the repository to be smaller.</p>
<p>After your remove the obj/ folders from the git repository I
would recommend you make an .gitignore so git doesn't track them
anymore. That way you don't commit the binaries by accident later
on. We've made a little knowledge base article on how you make a
basic .gitignore file here <a href=
"http://support.appharbor.com/kb/tips-and-tricks/gitignore">http://support.appharbor.com/kb/tips-and-tricks/gitignore</a></p>
<p>Hope this helps or feel free to contact us again if you need
more help with this.</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T06:43:56Z2011-07-28T22:40:52ZMissing Reference<div><p>Okay, this make good sense. I'll make the changes and try it
again tomorrow.<br>
Thanks for your quick response and quality support.</p>
<p>Don</p>
<p>On Fri, Apr 15, 2011 at 11:40 PM, Rune Sørensen <<br>
<a href=
"mailto:tender+d62a60db2dadc8fa3a7d1ded400569eeb98407d90@tenderapp.com">
tender+d62a60db2dadc8fa3a7d1ded400569eeb98407d90@tenderapp.com</a>>
wrote:</p></div>donniefitz2tag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T06:54:40Z2011-07-28T22:40:52ZMissing Reference<div><p>I decided to just try adding the Unity dll's to the Dependencies
folder and<br>
that did it. Everything builds and the tests pass. Again, thanks.
You guys<br>
are doing a great thing with this system.</p>
<p>Don</p></div>donniefitz2tag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T06:59:42Z2011-07-28T22:40:52ZMissing Reference<div><p>So, after working with AH support, all I needed to do was add my
Microsoft.Practices.Unity references to a local folder in the
project (called Dependencies in my case) and then reference Unity
from that folder and all was well (because that folder is known by
Git). Apparently, Unity was referenced from my local machine but
adding the references to the git project (in the Dependencies
folder) did the trick.</p></div>donniefitz2tag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T07:01:17Z2011-04-16T07:01:17ZMissing Reference<div><p>Great - we're glad to hear everything worked out!</p>
<p>Thanks,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T07:04:36Z2011-07-28T22:40:52ZMissing Reference<div><p>I didn't have to add the ignore to Git. I just had to put the
dll's in the<br>
local Dependencies directory so Git knew about them. It was really
pretty<br>
clear after you explained it.</p>
<p>Don</p>
<p>On Sat, Apr 16, 2011 at 12:01 AM, Rune Sørensen <<br>
<a href=
"mailto:tender+d62a60db2dadc8fa3a7d1ded400569eeb98407d90@tenderapp.com">
tender+d62a60db2dadc8fa3a7d1ded400569eeb98407d90@tenderapp.com</a>>
wrote:</p></div>donniefitz2tag:support.appharbor.com,2010-11-23:Comment/66738052011-04-16T07:29:49Z2011-04-16T07:29:49ZMissing Reference<div><p>Yeah I know - I just wanted to recommend you to remove those
folders and ignoring them as it could make debugging these kinds of
errors easier in the future. You could then easily run "git clean
-fdx" (remove all files not tracked by git) and build it from
scratch. That would resemble how it's build on AppHarbor a bit
more. But great that it's more clear now :-)</p></div>rune