I'm working with Web Connection version 5.43, which I upgraded from an old 4.x version I had, but never used.
I am using such a small fraction of Rick's awesome product, just the core libraries - I hard code everything, that I'm sure 5.43 is fine for my needs.
I've tested the EXE and the COM builds on my development laptop. Actually, I've only tested the EXE version. The COM version loads and responds to the test, but I haven't figured out how to make it work on my laptop IIS.
Now the website app is ready to deploy and because I'm doing this all as a favor for a friend and have no budget, I'm hoping to go with low cost hosting, like dngsolutions.net or www.discountasp.net.
I realize now that low cost also means neither service has a phone number I can call, so I'm hesitant to move off the blocks...
I understand that deploying the EXE is much easier. Does anyone know if either of these services will support that approach?
I'm a little confused between the reference to an "EXE based COM server", which requires VFP run time files, and "COM operation", which apparently doesn't. More than confused, clueless probably better describes it.
Will I be able to run the Management Console on these hosting services? As far as I can tell I will not have server console access.
Finally, should I upgrade to WC 5.6+, which I understand will make it easier to do a COM deployment? If it makes a big difference I'll do it.
It's all a bit daunting. Nevertheless, I will slog my way through, but any advice appreciated!!!
Thanks.
There is a topic in the newest documentation titled "Deploying to Low Cost ASP.NET Hosts" you want to look at. It is available online or might be included in your present version (not sure about the version you have and what was included at the time).
--Harvey
Hi All,
I'm working with Web Connection version 5.43, which I upgraded from an old 4.x version I had, but never used.
I am using such a small fraction of Rick's awesome product, just the core libraries - I hard code everything, that I'm sure 5.43 is fine for my needs.
I've tested the EXE and the COM builds on my development laptop. Actually, I've only tested the EXE version. The COM version loads and responds to the test, but I haven't figured out how to make it work on my laptop IIS.
Now the website app is ready to deploy and because I'm doing this all as a favor for a friend and have no budget, I'm hoping to go with low cost hosting, like dngsolutions.net or www.discountasp.net.
I realize now that low cost also means neither service has a phone number I can call, so I'm hesitant to move off the blocks...
I understand that deploying the EXE is much easier. Does anyone know if either of these services will support that approach?
I'm a little confused between the reference to an "EXE based COM server", which requires VFP run time files, and "COM operation", which apparently doesn't. More than confused, clueless probably better describes it.
Will I be able to run the Management Console on these hosting services? As far as I can tell I will not have server console access.
Finally, should I upgrade to WC 5.6+, which I understand will make it easier to do a COM deployment? If it makes a big difference I'll do it.
It's all a bit daunting. Nevertheless, I will slog my way through, but any advice appreciated!!!
Thanks.
--hm--
I thought I had seen that documentation somewhere, probably on the web as its not in my copy of the wconnect.chm.
Looks like 5.6 is the way to go.
I think if you upgrade to the most current version your code will all run without needing to make modifications. The biggest difference will be the ability to use the most up to date code and the dot NET Managed Handler interface. The dot NET piece is important for you because you want a low cost hosting company or for that matter almost all hosting companies will have a problem with wc.exe running in COM mode on there systems. This is because of the configuration requirements. So the dot NET Managed Handler takes care of all of this. In the WC documentation sometimes the managed handler is referred to as just ".NET Handler" if you go searching for it.
There is a topic in the newest documentation titled "Deploying to Low Cost ASP.NET Hosts" you want to look at. It is available online or might be included in your present version (not sure about the version you have and what was included at the time).
--Harvey
Hi All,
I'm working with Web Connection version 5.43, which I upgraded from an old 4.x version I had, but never used.
I am using such a small fraction of Rick's awesome product, just the core libraries - I hard code everything, that I'm sure 5.43 is fine for my needs.
I've tested the EXE and the COM builds on my development laptop. Actually, I've only tested the EXE version. The COM version loads and responds to the test, but I haven't figured out how to make it work on my laptop IIS.
Now the website app is ready to deploy and because I'm doing this all as a favor for a friend and have no budget, I'm hoping to go with low cost hosting, like dngsolutions.net or www.discountasp.net.
I realize now that low cost also means neither service has a phone number I can call, so I'm hesitant to move off the blocks...
I understand that deploying the EXE is much easier. Does anyone know if either of these services will support that approach?
I'm a little confused between the reference to an "EXE based COM server", which requires VFP run time files, and "COM operation", which apparently doesn't. More than confused, clueless probably better describes it.
Will I be able to run the Management Console on these hosting services? As far as I can tell I will not have server console access.
Finally, should I upgrade to WC 5.6+, which I understand will make it easier to do a COM deployment? If it makes a big difference I'll do it.
It's all a bit daunting. Nevertheless, I will slog my way through, but any advice appreciated!!!
Thanks.
Running on a low cost host is not super easy unfortunately because of the special requirements for running Visual FoxPro without a full installation. You can run either in file based mode (as a manually launched EXE) or as COM server. The latter is fairly complex but once configured will be more reliable. The former can be done as long as the security setup allows for FULL TRUST operation.
Details can be foudn in this help topic:
http://www.west-wind.com/webconnection/docs/?page=_3c80pe77z.htm
+++ Rick ---
Hi All,
I'm working with Web Connection version 5.43, which I upgraded from an old 4.x version I had, but never used.
I am using such a small fraction of Rick's awesome product, just the core libraries - I hard code everything, that I'm sure 5.43 is fine for my needs.
I've tested the EXE and the COM builds on my development laptop. Actually, I've only tested the EXE version. The COM version loads and responds to the test, but I haven't figured out how to make it work on my laptop IIS.
Now the website app is ready to deploy and because I'm doing this all as a favor for a friend and have no budget, I'm hoping to go with low cost hosting, like dngsolutions.net or www.discountasp.net.
I realize now that low cost also means neither service has a phone number I can call, so I'm hesitant to move off the blocks...
I understand that deploying the EXE is much easier. Does anyone know if either of these services will support that approach?
I'm a little confused between the reference to an "EXE based COM server", which requires VFP run time files, and "COM operation", which apparently doesn't. More than confused, clueless probably better describes it.
Will I be able to run the Management Console on these hosting services? As far as I can tell I will not have server console access.
Finally, should I upgrade to WC 5.6+, which I understand will make it easier to do a COM deployment? If it makes a big difference I'll do it.
It's all a bit daunting. Nevertheless, I will slog my way through, but any advice appreciated!!!
Thanks.
West Wind Technologies
Making waves on the Web
from Maui