Home → Support →

I'm referencing an assembly that is not in AppHarbor, can I add references to 3rd party assemblies? How do I put them into AppHarbor?

• Edit

mlsteeves

07 Mar, 2011 11:48 PM

Here is the error test I get when my app compiles on AppHarbor. The assembly in questions (I believe) is entitiy framework CTP5. How do I get those assembly into AppHarbor, and maybe I can't?

c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1360,9): warning MSB3245: Could not resolve this reference. Could not locate the assembly "EntityFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

1. Support Staff 1 Posted by friism on 07 Mar, 2011 11:59 PM

   

   Sure you can. Right click the reference in Visual Studio -> properties -> Set Copy Local to True. Try pushing again.

   • Edit

2. friism closed this discussion on 07 Mar, 2011 11:59 PM.

3. mlsteeves re-opened this discussion on 08 Mar, 2011 12:20 AM

4. 2 Posted by mlsteeves on 08 Mar, 2011 12:20 AM

   

   Does this mean that my output directories should be part of what gets pushed
   in git? (Usually I ignore build directories in my repositories). Or maybe
   I am mistaken on what "Copy Local" does.

   Thanks for the quick reply btw, that is awesome!!

   On Mon, Mar 7, 2011 at 8:00 PM, Michael Friis <
   [email blocked]> wrote:

   • Edit

5. Support Staff 3 Posted by friism on 08 Mar, 2011 12:27 AM

   

   "Copy Local" means that, as part of the build, the referenced dll is copied to the output directory. You're right that pushing your local output directories is generally a bad idea and for that reason, the 3rd party dlls you reference should be placed in a lib folder or similar. That lib folder should be part of the code you push.

   • Edit

6. friism closed this discussion on 08 Mar, 2011 12:27 AM.