Re: RE: example VB.net xAP apps and docs?

[Kevin Hawkins <yahoogroupskh@xxxxxxxxxxxxxx>]

I have a xAP BSC Framework - which is basically all the code you need
to
implement a BSC device model in VB6.  It originally used Patricks OCX
but due to the memory leak in that I swapped it to the Intranet OCX and
updated it to xAP v1.3 It is effectively documented within the source
code but it still needs a bit of attention before being 'prime time' .
Works though... but is in in VB6.   If that's any use to you then shout
- but it won't just convert to a VB.Net application and I don't want to
get involved in doing that either as xFX is far more suitable.

There are other VB6 applications around with source code availability -
and IIRC James has some Intranet OCX examples - the xAP bit is
effectively all done for you by the OCX :-)

Kevin

Paul Gale wrote:
>
> Ah OK - that sounds promising - I'll take a look at it.
>
> Are there any code samples for xAP VB6 apps?
>
> Paul.
>
> -----Original Message-----
> From: xap_automation@xxxxxxx
> <mailto:xap_automation%40yahoogroups.com>
> [mailto:xap_automation@xxxxxxx
> <mailto:xap_automation%40yahoogroups.com>]
On Behalf Of Kevin Hawkins
> Sent: 16 February 2009 16:15
> To: xap_automation@xxxxxxx
> <mailto:xap_automation%40yahoogroups.com>
> Subject: Re: [xap_automation] RE: example VB.net xAP apps and docs?
>
> For VB6 my recommendation would be to use James' xAP Intranet OCX
which
> is fairly well documented on the mi4 site - Plus I have used it so I
> will be able to help a little there too. You could use it from VB.Net
> too I believe....
>
> K
>
> Paul Gale wrote:
> >
> >
> >
> > Are there any docs for the VB6 based xAP framework - that may at
least
> > give me an idea of how much code is needed and the complexity,
even if
> > xFx is reasonably different???
> >
> > Cheers,
> >
> > Paul.
> >
> >
>
> ------------------------------------
>
> Yahoo! Groups Links
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 3856 (20090216) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
<http://www.eset.com>
>
>



------------------------------------