RE: xAP framework based apps problem

["Edward Pearson" <edward.mailgroup@xxxxxxxxxxxxxxxx>]

------=_NextPart_000_0003_01C53059.B157A1A0
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit

1. That's great news - you're back up and running :-)
2. That's the worst result, unless we find out more, since we've learnt
nothing :-(

Ah, technology!

_____

From: David Pullen [mailto:dpullen@xxxxxxx]
Sent: 24 March 2005 09:53
To: xap_automation@xxxxxxx
Subject: RE: [xap_automation] xAP framework based apps problem



The good news is that the problem has now disappeared. The bad news is that
I am not entirely sure what fixed it! The only changes that I can remember
since it was last not working are:

*       Running the EXEs supplied by Stuart
*       Compiling the new EXEs
*       Replacing the Homeseer conduit testv2 with testv3
*       Redetecting devices in Homeseer
*       Shutting down the system for the night
*       Starting up
*       Re-installing Netiom-xAP interface software (I had uninstalled in
case it was causing the problem)


The service hub had not started at start-up which is the normal situation
with the problem. So that suggests the problem may not have resolved itself
until AFTER start-up today. I have just shutdown and restarted and the
service hub did start up.

I will report any more information but I must admit it is a bit of a
mystery.

BR

David



-----Original Message-----
From: David Pullen [mailto:dpullen@xxxxxxx]
Sent: 23 March 2005 22:52
To: xap_automation@xxxxxxx
Subject: RE: [xap_automation] xAP framework based apps problem


Stuart

I have also run CSC on class1.cs under both versions of .NET. Both EXEs

worked.

BR

David

-----Original Message-----

From: Stuart Booth [mailto:lists@xxxxxxx]

Sent: 23 March 2005 19:22

To: xap_automation@xxxxxxx

Subject: Re: [xap_automation] xAP framework based apps problem


David,

Try this (4k download):

http://www.xapframework.net/Downloads/Beta/IPAddress.zip

This is a copy of an example I found on Google of somebody having the

same problem as yourself. It's a REALLY simple application. I've

compiled it in VS.NET 2003 as a C# and a VB.NET application (binaries

included), and I've included the source code too.

How about trying both EXEs to see if they get this type initialisation

error. If they do, you could try compiling up the VB.NET code in your

VB.NET s/w, but based on comments on the web, I suspect this'll work.

Now, I reckon you can use the C# compiler that comes with the .NET

Framework v1.1 to compile the C# source file. You'll need to have

C:\WinNT\Microsoft.NET\Framework\v1.1.4322 in your path I suspect but

if you go "CSC class1.cs" you should end up with a Class1.exe
file. I

anticipate that if the supplied binary failed, this will too.

Anyway, give that a spin??

S

--

Stuart Booth <stuart@xxxxxxx>

xAPFramework.NET - a xAP software development framework for .NET

http://www.xapautomation.org/ 
     http://www.xapframework.net/