]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Gimelfarb
Sent: Saturday, May 22, 2004 7:01 PM
To: [EMAIL PROTECTED]
Subject: RE: [Mono-list] A Plugin and WebService Issue
Since you generate the code from WSDL, why don't you preparse the WSDL doc
to see whether it contains the needed methods. WSDL
Fischer [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 20, 2004 5:04 PM
To: [EMAIL PROTECTED]
Subject: Re: [Mono-list] A Plugin and WebService Issue
Thanks people!
When I start writing my app (mbloggy) I was using Interfaces as plugins
(xmlrpc plugins), then I started reading
]
Sent: Saturday, May 22, 2004 6:00 PM
To: [EMAIL PROTECTED]
Subject: RE: [Mono-list] A Plugin and WebService Issue
Sure,
I'd like to be sure that the plugin of the user has a 'Post' method
for
example, or a 'DeletePost', if all the 'rules' are ok the code
22, 2004 11:10 AM
To: [EMAIL PROTECTED]
Subject: RE: [Mono-list] A Plugin and WebService Issue
But that is after compiling the code, right?, with the MethodInfo, Get,
Invoke methods.
I know that I can do this when the assembly is already compiled, but I'd
like to do this BEFORE
Could you tell us why you want to check the code?
Greetz,
-- Rob.
-Original Message-
From: Pablo Fischer [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 20, 2004 5:04 PM
To: [EMAIL PROTECTED]
Subject: Re: [Mono-list] A Plugin and WebService Issue
Thanks people!
When I start writing my
http://primates.ximian.com/~miguel//texts/cli-plugins.html
tor 2004-05-20 klockan 03.14 skrev Pablo Fischer:
Hi!
I would like to have some comments and suggestions about a issue.
I am working in a Blog Client (mbloggy) that will work ONLY in SOAP (NO
XMLRPC) for different CMS and Blogs
Hi,
I would use this approach:
1) you must have a plug-in Interface defined, that each plug-in must
implement
2) when the application starts, use static System.IO.Directory.GetFiles()
method to get the names of assemblies in the plug-in directory
3) for each plug-in-assembly file call static
The common approach on the net seems to be the following:
Define an interface, let's say IMyPlugin. this interface ideally should have a
method allowing you to supply a set of parameters needed to init the plugin's
main class, by say, passing params[] or something of the kind.
Then, you make
