That is the rule because the compiler need to know the details of the
Interface that is defined A because it is being used publicly as your
public class implements it.
As assembly references aren't transitive you need to be explicit (to embed
proper dependency versioning metadata) about which
Hi,
Thanks for the answer. This seemed not to be the case with the M$
compiler. I will double check today.
Is there any way to build 'fat libraries' (standalone) i.e to tell
the compiler to put everything that the library needs (of course not
mscorlib) in the library itself?
Cheers,
Search for ilmerge it can do this after the compilation.
On Mon, Nov 25, 2013 at 5:27 PM, Vassil Vassilev v.g.vassi...@gmail.comwrote:
Hi,
Thanks for the answer. This seemed not to be the case with the M$
compiler. I will double check today.
Is there any way to build 'fat libraries'
Is there any obvious advantage of ilmerge over adding all relevant files
when building that library. I.e expanding the references. I can afford
that because in our home-grown cmake csharp module keeps track of the
dependencies.
Vassil
On 11/25/2013 04:58 PM, Greg Young wrote:
Search for
Is there a logic to how I would work out what the latest Stable branch is?
What I mean by this is the branch that is considered to be bug fix only?
Basically, I'm trying to workout what is the best source to compile for a
production machine as I'm running ubuntu and don't want to stick with the
Hi,
If anyone has an insight, experience or even hint on this one, this would be
greatly appreciated.
I have a C# application that loads the a native shared library (the R shared
library). I use DllImport as follows:
[DllImport(libdl)]
private static extern IntPtr
On Nov 25, 2013, at 5:47 PM, jean-michel.perr...@csiro.au wrote:
[DllImport(libdl)]
[return: MarshalAs(UnmanagedType.LPStr)]
private static extern string dlerror();
You should (almost?) never use `string` (or any other reference type) as the
return type in a P/Invoke method:
