[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: RE: Slim Conduit Feature request vs. GUI Plugin bits feat. MC
Booth and the plugin boys
- Subject: RE: RE: Slim Conduit Feature request vs. GUI Plugin
bits feat. MC Booth and the plugin boys
- From: Edward Pearson
- Date: Tue, 30 Mar 2004 00:15:00 +0000
Cool, I'll drop the code snippet in...
> location, works fine, although I don't have my CM12U plugged in:
So plug it in!
:-)
"Standard MC" - Make the lights flash faster
> -----Original Message-----
> From: Stuart Booth [mailto:<a
href="/group/xAP_developer/post?postID=cFfCwsJI3pIjHrzPrOEnMv0TUGpLPYnqLMCTqaL4Oo3YJTgaejL52TTLYFbc6v438ByBxDv2UJPpgO7Uwg">lists@x...</a>]
> Sent: 29 March 2004 22:53
> To: <a
href="/group/xAP_developer/post?postID=4D47pLpv02xN9XaInS7W-qjTSKvFF2q0s2y-7DKdI8BrRaU7UgMGN73cGh_OI65Lz8UKCcKNucUwrJ94vqFRBsdhM_VqMGkL">xAP_developer@xxxxxxx</a>
> Subject: Re: [xAP_developer] RE: Slim Conduit Feature request
> vs. GUI Plugin bits feat. MC Booth and the plugin boys
>
>
> On Sun, 28 Mar 2004 17:06:00 +0100, "Edward Pearson"
> <<a
href="/group/xAP_developer/post?postID=CxzQiWTEcENlp0tfQG3BhZRbKtEG4h7C46fVuwF11gVcYdqTXjiN9utb8_C-imvog_uiA39ZKdzh9Zy0if5okOlWeZCLSKs8ZnS4">edward.mailgroup@b...</a>>
wrote:
>
> >Here's a version of the X10 connector to check out. It uses the
xml
> >file to store its properties. Only the serialport setting is taken
> >notice of at the moment. So I think (but I'm not sure) that the
.dll
> >goes in the plugins folder of the GUI runtime and the .xml
> file goes in
> >the same folder as the runtime exe. Stuart fancy checking it out
> >quickly?
>
> The XML file seems to need to go in the same directory as the
> EXE file. It barfs if it isn't present if it isn't located
> there, and the plugin won't load. But when it's in the right
> location, works fine, although I don't have my CM12U plugged in:
>
<a href="http://www.xapframework.net/xAPImages/X10Connector.jpg">http://www.xapframework.net/xAPImages/X10Connector.jpg</a>
My own config files sit alongside the plugin DLL in the Plugins folder as
you expected. Somehow, can't remember how it happens, that's the path that
they expect to find themselves in. I suspect I examine the
Assembly.GetExecutingAssembly object for its location... yes, here we go,
this is what the SlimServer Connector does:
private static FileInfo BuildProfileFilename ()
{
String assembly = Assembly.GetExecutingAssembly().Location;
assembly = Path.ChangeExtension(assembly, ".xml");
return new FileInfo (assembly);
} // End of BuildProfileFilename
I'll be covering all this in a future edition of the "xFx Developer
Magazine" but if you have any queries, fire away, as it'll be useful
for
when I come to write this.
MC "Stub"
--
Stuart Booth <<a
href="/group/xAP_developer/post?postID=Cnwm8LQborScyjqSkAQ6_9GLJN_aDEtIJRLBOOxjOOdgGkBJ-gU1gwUXx8OrKlAYHZlg_x46iABf-EKnjWVKsQ">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net
<a href="http://www.xapautomation.org/">http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/">http://www.xapframework.net/</a>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|