The open source version on Github uses a different DLL, so you need to switch to that dll if you use that (ClrHost.dll I think).
The reason for this is that wwIpstuff.dll contains a bunch of other stuff, but ClrHost only contains the .NET runtime hosting bootstrap code. You can run both if necessary or you can switch the define in wwdotnetbridge.dll. I think the wwipstuff.dll loader should work jsut fine with the open source version since that never changes. Just change the #DEFINE IS_WESTWIND .T. at the top of wwdotnetbridge.prg.
+++ Rick ---
I upgraded wwDotNetBridge.dll version 5.66 (the version I had in client tools) to version 5.68 (from Github) and now I get "Cannot find entry point SetClrVersion in the DLL." There is literally no difference in the machine apart from the wwDotNetBridge version.
West Wind Technologies
Making waves on the Web
from Maui
Edit: Small progress, and apologies for asking but I'm an old programmer who's been thrown into this new fangled .NET stuff, but I get so far with this code:
do wwDotNetBridge
local loBridge as wwDotNetBridge
loBridge = createobject("wwDotNetBridge", "V2")
if !loBridge.LoadAssembly("TAAP.Graphics.dll")
? "Error:", loBridge.cErrorMsg
return
endif
? "OK"
loSig = loBridge.CreateInstance("TAAP.Graphics.Signature", cXML)
if loBridge.lError
? "Error:", loBridge.cErrorMsg
return
endif
? vartype(loSig)
loSig is an object but any attempt to access it just produces "OLE error code 0x80131509: Unknown COM status code."
The open source version on Github uses a different DLL, so you need to switch to that dll if you use that (ClrHost.dll I think).
The reason for this is that wwIpstuff.dll contains a bunch of other stuff, but ClrHost only contains the .NET runtime hosting bootstrap code. You can run both if necessary or you can switch the define in wwdotnetbridge.dll. I think the wwipstuff.dll loader should work jsut fine with the open source version since that never changes. Just change the #DEFINE IS_WESTWIND .T. at the top of wwdotnetbridge.prg.
+++ Rick ---
I upgraded wwDotNetBridge.dll version 5.66 (the version I had in client tools) to version 5.68 (from Github) and now I get "Cannot find entry point SetClrVersion in the DLL." There is literally no difference in the machine apart from the wwDotNetBridge version.
The OSS version also is a little behind in versions usually - typically the Web Connection version is the first to see changes and fixes with updates for Client Tools and OSS versions later.
Hope that helps,
+++ Rick ---
Thanks, Rick. Setting IS_WESTWIND did the trick. Is there any advantage in using the opensource version over the version in Client tools or using ClrHost rather than wwipstuff? Is there an update to the client tools and how do I get it?
Edit: Small progress, and apologies for asking but I'm an old programmer who's been thrown into this new fangled .NET stuff, but I get so far with this code:
do wwDotNetBridge
local loBridge as wwDotNetBridge
loBridge = createobject("wwDotNetBridge", "V2")
if !loBridge.LoadAssembly("TAAP.Graphics.dll")
? "Error:", loBridge.cErrorMsg
return
endif
? "OK"
loSig = loBridge.CreateInstance("TAAP.Graphics.Signature", cXML)
if loBridge.lError
? "Error:", loBridge.cErrorMsg
return
endif
? vartype(loSig)
loSig is an object but any attempt to access it just produces "OLE error code 0x80131509: Unknown COM status code."
The open source version on Github uses a different DLL, so you need to switch to that dll if you use that (ClrHost.dll I think).
The reason for this is that wwIpstuff.dll contains a bunch of other stuff, but ClrHost only contains the .NET runtime hosting bootstrap code. You can run both if necessary or you can switch the define in wwdotnetbridge.dll. I think the wwipstuff.dll loader should work jsut fine with the open source version since that never changes. Just change the #DEFINE IS_WESTWIND .T. at the top of wwdotnetbridge.prg.
+++ Rick ---
I upgraded wwDotNetBridge.dll version 5.66 (the version I had in client tools) to version 5.68 (from Github) and now I get "Cannot find entry point SetClrVersion in the DLL." There is literally no difference in the machine apart from the wwDotNetBridge version.
West Wind Technologies
Making waves on the Web
from Maui
Any pointers on why I might be getting the OLE error? I have upload ther DLL I have to work with: TAAPGraphics
The code for the OSS version and the one that ships with our products is the same for wwDotnetBridge, but the Web Connection/Client Tools version contains additional functiality specific to those tools. There are other classes in there like wwSmtp, some WSDL parsing code and other utility code that is specific to other West Wind stuff. That stuff doesn't exist in the OSS version.
The OSS version also is a little behind in versions usually - typically the Web Connection version is the first to see changes and fixes with updates for Client Tools and OSS versions later.
Hope that helps,
+++ Rick ---
Thanks, Rick. Setting IS_WESTWIND did the trick. Is there any advantage in using the opensource version over the version in Client tools or using ClrHost rather than wwipstuff? Is there an update to the client tools and how do I get it?
Edit: Small progress, and apologies for asking but I'm an old programmer who's been thrown into this new fangled .NET stuff, but I get so far with this code:
do wwDotNetBridge
local loBridge as wwDotNetBridge
loBridge = createobject("wwDotNetBridge", "V2")
if !loBridge.LoadAssembly("TAAP.Graphics.dll")
? "Error:", loBridge.cErrorMsg
return
endif
? "OK"
loSig = loBridge.CreateInstance("TAAP.Graphics.Signature", cXML)
if loBridge.lError
? "Error:", loBridge.cErrorMsg
return
endif
? vartype(loSig)
loSig is an object but any attempt to access it just produces "OLE error code 0x80131509: Unknown COM status code."
The open source version on Github uses a different DLL, so you need to switch to that dll if you use that (ClrHost.dll I think).
The reason for this is that wwIpstuff.dll contains a bunch of other stuff, but ClrHost only contains the .NET runtime hosting bootstrap code. You can run both if necessary or you can switch the define in wwdotnetbridge.dll. I think the wwipstuff.dll loader should work jsut fine with the open source version since that never changes. Just change the #DEFINE IS_WESTWIND .T. at the top of wwdotnetbridge.prg.
+++ Rick ---
I upgraded wwDotNetBridge.dll version 5.66 (the version I had in client tools) to version 5.68 (from Github) and now I get "Cannot find entry point SetClrVersion in the DLL." There is literally no difference in the machine apart from the wwDotNetBridge version.
Than you, Rick. I think I'll go back to using the Client Tools then. How do I update from version 5.66 to 5.68?
Any pointers on why I might be getting the OLE error? I have upload ther DLL I have to work with: TAAPGraphics
The code for the OSS version and the one that ships with our products is the same for wwDotnetBridge, but the Web Connection/Client Tools version contains additional functiality specific to those tools. There are other classes in there like wwSmtp, some WSDL parsing code and other utility code that is specific to other West Wind stuff. That stuff doesn't exist in the OSS version.
The OSS version also is a little behind in versions usually - typically the Web Connection version is the first to see changes and fixes with updates for Client Tools and OSS versions later.
Hope that helps,
+++ Rick ---
Thanks, Rick. Setting IS_WESTWIND did the trick. Is there any advantage in using the opensource version over the version in Client tools or using ClrHost rather than wwipstuff? Is there an update to the client tools and how do I get it?
Edit: Small progress, and apologies for asking but I'm an old programmer who's been thrown into this new fangled .NET stuff, but I get so far with this code:
do wwDotNetBridge
local loBridge as wwDotNetBridge
loBridge = createobject("wwDotNetBridge", "V2")
if !loBridge.LoadAssembly("TAAP.Graphics.dll")
? "Error:", loBridge.cErrorMsg
return
endif
? "OK"
loSig = loBridge.CreateInstance("TAAP.Graphics.Signature", cXML)
if loBridge.lError
? "Error:", loBridge.cErrorMsg
return
endif
? vartype(loSig)
loSig is an object but any attempt to access it just produces "OLE error code 0x80131509: Unknown COM status code."
The open source version on Github uses a different DLL, so you need to switch to that dll if you use that (ClrHost.dll I think).
The reason for this is that wwIpstuff.dll contains a bunch of other stuff, but ClrHost only contains the .NET runtime hosting bootstrap code. You can run both if necessary or you can switch the define in wwdotnetbridge.dll. I think the wwipstuff.dll loader should work jsut fine with the open source version since that never changes. Just change the #DEFINE IS_WESTWIND .T. at the top of wwdotnetbridge.prg.
+++ Rick ---
I upgraded wwDotNetBridge.dll version 5.66 (the version I had in client tools) to version 5.68 (from Github) and now I get "Cannot find entry point SetClrVersion in the DLL." There is literally no difference in the machine apart from the wwDotNetBridge version.
Not without looking at the component...
Please make sure that wwDotnetBridge otherwise works. Look at some of the samples and make sure those work and don't give you the same error.
If you get a COM error when instantiating the object, there's not a lot that can be done to work around that. Most likely the object has something in it that can't travel over COM. There might be workarounds for that, but I'd have to take a look at it.
+++ Rick ---
Sorry to be a pain but do you have any ideas or at least any suggestions as to where I can research with regard to the OLE error? I really would be very grateful for a reply as I've got a customer project that has stalled because of this.
Than you, Rick. I think I'll go back to using the Client Tools then. How do I update from version 5.66 to 5.68?
Any pointers on why I might be getting the OLE error? I have upload ther DLL I have to work with: TAAPGraphics
The code for the OSS version and the one that ships with our products is the same for wwDotnetBridge, but the Web Connection/Client Tools version contains additional functiality specific to those tools. There are other classes in there like wwSmtp, some WSDL parsing code and other utility code that is specific to other West Wind stuff. That stuff doesn't exist in the OSS version.
The OSS version also is a little behind in versions usually - typically the Web Connection version is the first to see changes and fixes with updates for Client Tools and OSS versions later.
Hope that helps,
+++ Rick ---
Thanks, Rick. Setting IS_WESTWIND did the trick. Is there any advantage in using the opensource version over the version in Client tools or using ClrHost rather than wwipstuff? Is there an update to the client tools and how do I get it?
Edit: Small progress, and apologies for asking but I'm an old programmer who's been thrown into this new fangled .NET stuff, but I get so far with this code:
do wwDotNetBridge
local loBridge as wwDotNetBridge
loBridge = createobject("wwDotNetBridge", "V2")
if !loBridge.LoadAssembly("TAAP.Graphics.dll")
? "Error:", loBridge.cErrorMsg
return
endif
? "OK"
loSig = loBridge.CreateInstance("TAAP.Graphics.Signature", cXML)
if loBridge.lError
? "Error:", loBridge.cErrorMsg
return
endif
? vartype(loSig)
loSig is an object but any attempt to access it just produces "OLE error code 0x80131509: Unknown COM status code."
The open source version on Github uses a different DLL, so you need to switch to that dll if you use that (ClrHost.dll I think).
The reason for this is that wwIpstuff.dll contains a bunch of other stuff, but ClrHost only contains the .NET runtime hosting bootstrap code. You can run both if necessary or you can switch the define in wwdotnetbridge.dll. I think the wwipstuff.dll loader should work jsut fine with the open source version since that never changes. Just change the #DEFINE IS_WESTWIND .T. at the top of wwdotnetbridge.prg.
+++ Rick ---
I upgraded wwDotNetBridge.dll version 5.66 (the version I had in client tools) to version 5.68 (from Github) and now I get "Cannot find entry point SetClrVersion in the DLL." There is literally no difference in the machine apart from the wwDotNetBridge version.
West Wind Technologies
Making waves on the Web
from Maui
Not without looking at the component...
Please make sure that wwDotnetBridge otherwise works. Look at some of the samples and make sure those work and don't give you the same error.
If you get a COM error when instantiating the object, there's not a lot that can be done to work around that. Most likely the object has something in it that can't travel over COM. There might be workarounds for that, but I'd have to take a look at it.
+++ Rick ---
Sorry to be a pain but do you have any ideas or at least any suggestions as to where I can research with regard to the OLE error? I really would be very grateful for a reply as I've got a customer project that has stalled because of this.
Than you, Rick. I think I'll go back to using the Client Tools then. How do I update from version 5.66 to 5.68?
Any pointers on why I might be getting the OLE error? I have upload ther DLL I have to work with: TAAPGraphics
The code for the OSS version and the one that ships with our products is the same for wwDotnetBridge, but the Web Connection/Client Tools version contains additional functiality specific to those tools. There are other classes in there like wwSmtp, some WSDL parsing code and other utility code that is specific to other West Wind stuff. That stuff doesn't exist in the OSS version.
The OSS version also is a little behind in versions usually - typically the Web Connection version is the first to see changes and fixes with updates for Client Tools and OSS versions later.
Hope that helps,
+++ Rick ---
Thanks, Rick. Setting IS_WESTWIND did the trick. Is there any advantage in using the opensource version over the version in Client tools or using ClrHost rather than wwipstuff? Is there an update to the client tools and how do I get it?
Edit: Small progress, and apologies for asking but I'm an old programmer who's been thrown into this new fangled .NET stuff, but I get so far with this code:
do wwDotNetBridge
local loBridge as wwDotNetBridge
loBridge = createobject("wwDotNetBridge", "V2")
if !loBridge.LoadAssembly("TAAP.Graphics.dll")
? "Error:", loBridge.cErrorMsg
return
endif
? "OK"
loSig = loBridge.CreateInstance("TAAP.Graphics.Signature", cXML)
if loBridge.lError
? "Error:", loBridge.cErrorMsg
return
endif
? vartype(loSig)
loSig is an object but any attempt to access it just produces "OLE error code 0x80131509: Unknown COM status code."
The open source version on Github uses a different DLL, so you need to switch to that dll if you use that (ClrHost.dll I think).
The reason for this is that wwIpstuff.dll contains a bunch of other stuff, but ClrHost only contains the .NET runtime hosting bootstrap code. You can run both if necessary or you can switch the define in wwdotnetbridge.dll. I think the wwipstuff.dll loader should work jsut fine with the open source version since that never changes. Just change the #DEFINE IS_WESTWIND .T. at the top of wwdotnetbridge.prg.
+++ Rick ---
I upgraded wwDotNetBridge.dll version 5.66 (the version I had in client tools) to version 5.68 (from Github) and now I get "Cannot find entry point SetClrVersion in the DLL." There is literally no difference in the machine apart from the wwDotNetBridge version.
http://west-wind.com/contact.aspx
+++ Rick ---
wwDotnetBridge is working fine. Is there any chance you'd be able to have a glance and tell me if it is a problem with their DLL? I don't want to be banging my head against a brick wall trying to get this thing working.
Not without looking at the component...
Please make sure that wwDotnetBridge otherwise works. Look at some of the samples and make sure those work and don't give you the same error.
If you get a COM error when instantiating the object, there's not a lot that can be done to work around that. Most likely the object has something in it that can't travel over COM. There might be workarounds for that, but I'd have to take a look at it.
+++ Rick ---
Sorry to be a pain but do you have any ideas or at least any suggestions as to where I can research with regard to the OLE error? I really would be very grateful for a reply as I've got a customer project that has stalled because of this.
Than you, Rick. I think I'll go back to using the Client Tools then. How do I update from version 5.66 to 5.68?
Any pointers on why I might be getting the OLE error? I have upload ther DLL I have to work with: TAAPGraphics
The code for the OSS version and the one that ships with our products is the same for wwDotnetBridge, but the Web Connection/Client Tools version contains additional functiality specific to those tools. There are other classes in there like wwSmtp, some WSDL parsing code and other utility code that is specific to other West Wind stuff. That stuff doesn't exist in the OSS version.
The OSS version also is a little behind in versions usually - typically the Web Connection version is the first to see changes and fixes with updates for Client Tools and OSS versions later.
Hope that helps,
+++ Rick ---
Thanks, Rick. Setting IS_WESTWIND did the trick. Is there any advantage in using the opensource version over the version in Client tools or using ClrHost rather than wwipstuff? Is there an update to the client tools and how do I get it?
Edit: Small progress, and apologies for asking but I'm an old programmer who's been thrown into this new fangled .NET stuff, but I get so far with this code:
do wwDotNetBridge
local loBridge as wwDotNetBridge
loBridge = createobject("wwDotNetBridge", "V2")
if !loBridge.LoadAssembly("TAAP.Graphics.dll")
? "Error:", loBridge.cErrorMsg
return
endif
? "OK"
loSig = loBridge.CreateInstance("TAAP.Graphics.Signature", cXML)
if loBridge.lError
? "Error:", loBridge.cErrorMsg
return
endif
? vartype(loSig)
loSig is an object but any attempt to access it just produces "OLE error code 0x80131509: Unknown COM status code."
The open source version on Github uses a different DLL, so you need to switch to that dll if you use that (ClrHost.dll I think).
The reason for this is that wwIpstuff.dll contains a bunch of other stuff, but ClrHost only contains the .NET runtime hosting bootstrap code. You can run both if necessary or you can switch the define in wwdotnetbridge.dll. I think the wwipstuff.dll loader should work jsut fine with the open source version since that never changes. Just change the #DEFINE IS_WESTWIND .T. at the top of wwdotnetbridge.prg.
+++ Rick ---
I upgraded wwDotNetBridge.dll version 5.66 (the version I had in client tools) to version 5.68 (from Github) and now I get "Cannot find entry point SetClrVersion in the DLL." There is literally no difference in the machine apart from the wwDotNetBridge version.
West Wind Technologies
Making waves on the Web
from Maui
http://west-wind.com/contact.aspx
+++ Rick ---
wwDotnetBridge is working fine. Is there any chance you'd be able to have a glance and tell me if it is a problem with their DLL? I don't want to be banging my head against a brick wall trying to get this thing working.
Not without looking at the component...
Please make sure that wwDotnetBridge otherwise works. Look at some of the samples and make sure those work and don't give you the same error.
If you get a COM error when instantiating the object, there's not a lot that can be done to work around that. Most likely the object has something in it that can't travel over COM. There might be workarounds for that, but I'd have to take a look at it.
+++ Rick ---
Sorry to be a pain but do you have any ideas or at least any suggestions as to where I can research with regard to the OLE error? I really would be very grateful for a reply as I've got a customer project that has stalled because of this.
Than you, Rick. I think I'll go back to using the Client Tools then. How do I update from version 5.66 to 5.68?
Any pointers on why I might be getting the OLE error? I have upload ther DLL I have to work with: TAAPGraphics
The code for the OSS version and the one that ships with our products is the same for wwDotnetBridge, but the Web Connection/Client Tools version contains additional functiality specific to those tools. There are other classes in there like wwSmtp, some WSDL parsing code and other utility code that is specific to other West Wind stuff. That stuff doesn't exist in the OSS version.
The OSS version also is a little behind in versions usually - typically the Web Connection version is the first to see changes and fixes with updates for Client Tools and OSS versions later.
Hope that helps,
+++ Rick ---
Thanks, Rick. Setting IS_WESTWIND did the trick. Is there any advantage in using the opensource version over the version in Client tools or using ClrHost rather than wwipstuff? Is there an update to the client tools and how do I get it?
Edit: Small progress, and apologies for asking but I'm an old programmer who's been thrown into this new fangled .NET stuff, but I get so far with this code:
do wwDotNetBridge
local loBridge as wwDotNetBridge
loBridge = createobject("wwDotNetBridge", "V2")
if !loBridge.LoadAssembly("TAAP.Graphics.dll")
? "Error:", loBridge.cErrorMsg
return
endif
? "OK"
loSig = loBridge.CreateInstance("TAAP.Graphics.Signature", cXML)
if loBridge.lError
? "Error:", loBridge.cErrorMsg
return
endif
? vartype(loSig)
loSig is an object but any attempt to access it just produces "OLE error code 0x80131509: Unknown COM status code."
The open source version on Github uses a different DLL, so you need to switch to that dll if you use that (ClrHost.dll I think).
The reason for this is that wwIpstuff.dll contains a bunch of other stuff, but ClrHost only contains the .NET runtime hosting bootstrap code. You can run both if necessary or you can switch the define in wwdotnetbridge.dll. I think the wwipstuff.dll loader should work jsut fine with the open source version since that never changes. Just change the #DEFINE IS_WESTWIND .T. at the top of wwdotnetbridge.prg.
+++ Rick ---
I upgraded wwDotNetBridge.dll version 5.66 (the version I had in client tools) to version 5.68 (from Github) and now I get "Cannot find entry point SetClrVersion in the DLL." There is literally no difference in the machine apart from the wwDotNetBridge version.
If for some reason the object can't be instantiated directly then the alternative is to create a custom assembly in .NET and instantiate the component from there then call that code from FoxPro.
+++ Rick ---
I understand. How much of your time do you think this will require?
http://west-wind.com/contact.aspx
+++ Rick ---
wwDotnetBridge is working fine. Is there any chance you'd be able to have a glance and tell me if it is a problem with their DLL? I don't want to be banging my head against a brick wall trying to get this thing working.
Not without looking at the component...
Please make sure that wwDotnetBridge otherwise works. Look at some of the samples and make sure those work and don't give you the same error.
If you get a COM error when instantiating the object, there's not a lot that can be done to work around that. Most likely the object has something in it that can't travel over COM. There might be workarounds for that, but I'd have to take a look at it.
+++ Rick ---
Sorry to be a pain but do you have any ideas or at least any suggestions as to where I can research with regard to the OLE error? I really would be very grateful for a reply as I've got a customer project that has stalled because of this.
Than you, Rick. I think I'll go back to using the Client Tools then. How do I update from version 5.66 to 5.68?
Any pointers on why I might be getting the OLE error? I have upload ther DLL I have to work with: TAAPGraphics
The code for the OSS version and the one that ships with our products is the same for wwDotnetBridge, but the Web Connection/Client Tools version contains additional functiality specific to those tools. There are other classes in there like wwSmtp, some WSDL parsing code and other utility code that is specific to other West Wind stuff. That stuff doesn't exist in the OSS version.
The OSS version also is a little behind in versions usually - typically the Web Connection version is the first to see changes and fixes with updates for Client Tools and OSS versions later.
Hope that helps,
+++ Rick ---
Thanks, Rick. Setting IS_WESTWIND did the trick. Is there any advantage in using the opensource version over the version in Client tools or using ClrHost rather than wwipstuff? Is there an update to the client tools and how do I get it?
Edit: Small progress, and apologies for asking but I'm an old programmer who's been thrown into this new fangled .NET stuff, but I get so far with this code:
do wwDotNetBridge
local loBridge as wwDotNetBridge
loBridge = createobject("wwDotNetBridge", "V2")
if !loBridge.LoadAssembly("TAAP.Graphics.dll")
? "Error:", loBridge.cErrorMsg
return
endif
? "OK"
loSig = loBridge.CreateInstance("TAAP.Graphics.Signature", cXML)
if loBridge.lError
? "Error:", loBridge.cErrorMsg
return
endif
? vartype(loSig)
loSig is an object but any attempt to access it just produces "OLE error code 0x80131509: Unknown COM status code."
The open source version on Github uses a different DLL, so you need to switch to that dll if you use that (ClrHost.dll I think).
The reason for this is that wwIpstuff.dll contains a bunch of other stuff, but ClrHost only contains the .NET runtime hosting bootstrap code. You can run both if necessary or you can switch the define in wwdotnetbridge.dll. I think the wwipstuff.dll loader should work jsut fine with the open source version since that never changes. Just change the #DEFINE IS_WESTWIND .T. at the top of wwdotnetbridge.prg.
+++ Rick ---
I upgraded wwDotNetBridge.dll version 5.66 (the version I had in client tools) to version 5.68 (from Github) and now I get "Cannot find entry point SetClrVersion in the DLL." There is literally no difference in the machine apart from the wwDotNetBridge version.
West Wind Technologies
Making waves on the Web
from Maui