Note that there are some explanatory texts on larger screens.

plurals
  1. POMonodevelop. Method that visible from Assembly Browser not found. (CS0584)
    primarykey
    data
    text
    <p>I have the .dll that is part of AForge.NET framework. I can't compile project because:</p> <pre><code>Error CS0584: Internal compiler error: Could not import type `AForge.Imaging.Filters.Sepia' from `AForge.Imaging, Version=2.2.4.0, Culture=neutral, PublicKeyToken=ba8ddea9676ca48b' (CS0584) (projectName) Error CS0584: Internal compiler error: Could not import type `AForge.Imaging.Filters.Invert' from `AForge.Imaging, Version=2.2.4.0, Culture=neutral, PublicKeyToken=ba8ddea9676ca48b' (CS0584) (projectName) Error CS0584: Internal compiler error: Method not found: 'AForge.Imaging.UnmanagedImage.CollectActivePixels'. (CS0584) (tryingImageProcessing) </code></pre> <p>But all of these methods and classes are visible from the assembly browser. <a href="http://dump.bitcheese.net/files/awitaje/ImageProcessing.zip/preview" rel="nofollow">Here is the link</a> to the project with error. I also <a href="https://bugzilla.xamarin.com/show_bug.cgi?id=6543" rel="nofollow">reported a bug</a> to xamarin bugzilla.</p> <p><em>Hope this post wouldn't be treated as copy of my previous: question of that post is completely different from current.</em> </p> <p><strong>UPDATE:</strong> Well, I've found what the problem was. @Jason was right: I haven't compiled libraries against MonoTouch, it was compiled against Mono. So I've created new projects and past sources there. AForge (Core) and AForge.Math compiled perfectly while AForge.Imaging hasn't: System.Drawing from github.com/mono/ implement some functions that AForge.Imaging needs. Hence, there is no solution by now. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload