Re: RE: Slim Conduit Feature request vs. GUI Plugin bits feat. MC Booth and the plugin boys

[Stuart Booth]

On Sun, 28 Mar 2004 17:06:00 +0100, "Edward Pearson"
<<a
href="/group/xAP_developer/post?postID=SR-GjOJwoIcYY1d4UweeMxVOQWalkEBugS1LvedPmFRjYofc7ymFI3Uxc_NM7Bmn9oieyiX8CWU8AaYPiQWLDQAoccu8AHOKllptvw">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=-YoBmyIG7OVaxH2-l9XvBierSJqYRH2ncMlxBKbqorGFmTkXxXfn9GnzHzmUFfos5-RpsC9iZRPLar66woFKdQ">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>