Hi Rick, The 7.02 install went without a hitch. The demo page was spawned and ran flawlessly.
However, when creating a new project, the project was not created. The folder structure was created, but still no project. Really no problem because I easily just created it manually but thought you should know.
Also, is there a reason for not including the wwAsyncServer form class in the distribution \classes folder? I still use it to spawn off special async request applications.
Any chance he has converted this VCX to a PRG like he did with other VCX libs?
I don't think so, it contains forms like his other vcx he kept.
No I removed that code because it's really old and just about nobody uses it 😃. If you're using it you're using a version that's 15+ years old, so you can use your old copy of it. And it's a VCX which as you know I'm trying to banish from Web Connection 😃. There's now only one left - wcvisual.vcx.
It's just one more piece of code I have to support and update and ship etc.
What should really happen is that that code should be updated to use the wwQueueMessageManager (which is the Fox client for the queue manager we built for MarvelPress) and then create the server form for that. But like I said there's practically no interest in this technology so at this point not worth the effort.
+++ Rick ---
I thought maybe it was accidentally forgotten since the corresponding wwAsyncWebRequest.prg is still distributed. I'll just have to remember to copy the two files over to wconnect\classes after each subsequent release. After copying over I was able to subclass and spawn off a new async service in a few minutes.
I can't believe more people aren't using this feature... It is the perfect lightweight VFP solution for offloading VFP reporting, emailing, and other various processes. Matt Slay has a really nice blog write-up on this here in case anyone is interested. http://mattslay.com/message-queue-solution-for-visual-foxpro-applications/
BTW, the new .NET Queue Message Manager is the bomb. https://github.com/RickStrahl/Westwind.QueueMessageManager I have it implemented with SQL Server and MSMQ, and have also implemented other features such as the Quartz scheduler http://www.quartz-scheduler.org/ (which you can have scheduled task run at certain times of the day using cron keys http://www.cronmaker.com/), Telerik report writer, and about 15 queues running various multiple threads. However for this particular lightweight project I am writing, I only have a couple vfp tables (so far 2, one is the async) so a whole new QMM application to SQL is plain overkill. WWC and Async pointing to vfp tables is perfect for this scenario, plus I get to use all the VFP reporting and other great VFP features.
