Hello dear developers,
I am Sebi and I'm currently developing an application which aims to do
massive encoding of queued movies
and of course, as open source supporter, I decided to use Mono as the
development environment for this application in my
company.
I am currently using Mono 1.2.6-1
Hi,
I don't know the exact status of COM support so if you need this information
you should wait for Jonathan Chambers.
You should be aware however that COM is a Windows specific technology so if
you want to use it I recommend you to use Microsoft .NET Framework that
should be compatible with
Sebi Onofrei wrote:
internet about how to solve my problems (such of not
implemented WebClient, WebRequest, WebResponse, etc... anyway using
sockets I managed to successfully create classes that
work like a charm)
Those classes are implemented since ages.
Robert
On Mon, 2008-03-03 at 11:58 +0200, Sebi Onofrei wrote:
The problem is that now I need to use COM communication. I will have to
use Flix Engine from On2 and as I discovered reading
their documentation / how-tos, I sorta' need this. (functions like
Type.GetTypeFromProgID(xyz) for example are
Does monodoc and the monodocer tools currently work on
Windows?
If it does, what do I need to do to create docs for an
assembly, such as, System.Data.OracleClient?
I haven't had too much success with these tools in the
past.
And with the results, how do i get it to work in
monodoc?
And how do
I personally prefer to have a phased deprecation including a period of
increasingly more annoying impediments. Here are some examples that
I've seen work:
* warning messages with feedback url
* enforced periods of delay prior to executing commands
* eventual removal of deprecated code and
Additionally, I believe that the Cecil-based mono-api-info is a
better implementation than the SRE-based implementation. And am
wondering if we should just replace our current implementation with the
version living in cecil (this would also eliminate mono-api-info and
mono-api-info2).
Well, if you look at the output you'll see that the cecil one is
considerably more condensed and readable than the SRE one, so that could
easily explain the filesize difference. For example, the 'ClearProps(in
System.Byte, in System.UInt32, in System.Guid, in System.Int32)' method
is 7 lines in
Right, it is more condensed because it is missing the rest of the
information. :)
For your example, it is missing the attributes on the parameters. Both
files should be exactly the same.
Jonathan
Alan McGovern wrote:
Well, if you look at the output you'll see that the cecil one is
On Mon, 2008-03-03 at 08:32 -0800, Daniel Morgan wrote:
Does monodoc and the monodocer tools currently work on
Windows?
Yes. They're also included with the Mono Windows download.
If it does, what do I need to do to create docs for an
assembly, such as, System.Data.OracleClient?
This change seems to break the build for me:
--- mono/metadata/verify.c (revision 97000)
+++ mono/metadata/verify.c (working copy)
@@ -235,6 +235,8 @@
static gboolean
token_bounds_check (MonoImage *image, guint32 token)
{
+ if (image-dynamic)
+ return
On Tue, 2008-02-26 at 15:20 +, Christian Stümpel wrote:
Hi everybody ,
since I got no reply I post this again. Please help...
Please fill a bug report and attach both your code and your GIF image.
my program analyzes System.Drawing.Bitmaps. Many pixel formats (all-
non indexed, some
12 matches
Mail list logo
