The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: xAP framework based apps problem


  • Subject: RE: xAP framework based apps problem
  • From: "David Pullen" <dpullen@xxxxxxxxxxxxxxxx>
  • Date: Wed, 23 Mar 2005 22:52:23 -0000


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/




xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.