Yes, the interface IXmlSerializable, but it's a "Use at your own risk" -
unsupported interface.
You might be able to work around the issue by overriding all properties of
an interface type and attaching the XmlIgnoreAttribute or by writing a
wrapper class that hides the problematic members and syn
On Thu, 22 May 2003 08:45:42 -0600, Mike Woodring (DevelopMentor)
<[EMAIL PROTECTED]> wrote:
>> Do publisher policies only work with assemblies installed within the
>> GAC?
>
>Correct.
>
I think to remember that the assembly must be strong named but it can be
out of the GAC while the Publisher Po
It is possible that your thread(s) didn't start before you called abort.
Try checking the ThreadState before calling abort to see.
-Jeff WS
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of John
Sent: Wednesday, May 28, 2003 2:08
Hello,
This is rather convoluted. Any help would be greatly appreciated.
I have an assembly that exports two calls to COM, ONE OF WHICH USES
System.Windows.Forms TO DISPLAY A DIALOG (this may be important).
I use the assembly in an application (written in LabVIEW, this may not
be important, but
Hi,
I am running the piece of code below, and I am getting an exception error
when trying to Abort the threads. This does not happen consistently
though, it is very random. What might be the problem here??
Thanks.
John
BarText = "Retrieving data ..";
StartProgThread(ThreadName);
OleDbData
>[Urs] You can implement another interface, I don't remember which one it is,
>to be serializable.
I think the interface you are talking about is IXmlSerializable. I think this should
work for you Brian. Its not documented though.
John
-Original Message-
From: Urs Muff [mailto:[EMAIL PR
> -Original Message-
> From: Thomas Tomiczek [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 28, 2003 9:39 AM
> To: [EMAIL PROTECTED]
>
> > -Original Message-
> > From: brian.nantz [mailto:[EMAIL PROTECTED]
> > Sent: Mittwoch, 28. Mai 2003 17:13
> > To: [EMAIL PROTECTED]
> >
> > Fi
> >// C#
> >public void LoadProperty( object o ){
> Log.Info( o.ToString() ); //CallPutSchedule
> Log.Info( o.GetType().ToString() ); //System.String
> o.GetType().GetMethods(); //Returns methods for
> System.String }
>
> >Would someone be able to explain this very perplex
>// C#
>public void LoadProperty( object o ){
Log.Info( o.ToString() ); //CallPutSchedule
Log.Info( o.GetType().ToString() ); //System.String
o.GetType().GetMethods(); //Returns methods for System.String }
>Would someone be able to explain this very perplexing behavior to m
> -Original Message-
> From: brian.nantz [mailto:[EMAIL PROTECTED]
> Sent: Mittwoch, 28. Mai 2003 17:13
> To: [EMAIL PROTECTED]
>
> First off I'm not sure why XMLSerialize can't handle
> interfaces. Isn't this kind of a bad restriction on a
> language that only has single inheritance a
Hi everyone,
(This is a repost from the CLR group, no one there had a response for
me, so hopefully someone here will)
-
I'm having a strange problem. Let me present it:
I have a bunch of Classes in .Net (C#). Most of them are accessible via
COM (I have supplied a Guid
First off I'm not sure why XMLSerialize can't handle interfaces. Isn't this
kind of a bad restriction on a language that only has single inheritance and
relies heavily on interfaces!
Here is my question. I have a barcode class that looks like this:
public class Barcode : Control, IComponen
12 matches
Mail list logo
