With all the woes that IIS has suffered (and also being a sentimental old bugger) it would be great for me to see Website Pro re emerge as a contender in the Webserver stakes.
Kind Regards - Mike Brunt, CTO Webapper http://www.webapper.com Downey CA Office 562.243.6255 AIM - webappermb "Webapper - Making the NET work" -----Original Message----- From: Michael Dinowitz [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 2:20 PM To: CF-Talk Subject: Re: CF MX works on WebSite Pro (was: RE: Ridiculous Problem!) 1. I happen to be one of those Website pro users and there are a lot more than three of us. Maybe even 5. :) 2. If you don't mind, I'd like to forward this to Bob Denny, who is working on the issue. If its an easy fix than I'd be exceptionally happy and I'm sure that many others will be as well. At 05:22 PM 6/5/02, you wrote: >> Let's be fair... CFMX is not setup to handle Website Pro. >> I have heard that Website Pro teams are working on something >> (according to someone on this list from last week) for CFMX, >> but ... if you look at the CFMX supported webservers, Website >> Pro is not one of them. > >I don't think Bud is running CF MX: > >"OK. I've got CF 4.51 on my development box. I also run WebSite >Pro on the dev box, which I just upgraded to the latest version, >which I'd also done on the real server with no problem." > > From this, I assume he just upgraded WebSite Pro, not CF. > >Anyway, what's more interesting is this - the prerelease versions of CF MX >used an ISAPI filter, and ISAPI filters aren't supported by WebSite Pro. The >release version, on the other hand, uses an ISAPI extension, and WebSite Pro >supports those. > >So, since I had a copy of WebSite Pro, I decided to install it on my CF MX >machine, and they work together fine (CF MX, WebSite Pro 3.1.13 SP1). Note >that, to get it working, I already had CF MX in standalone mode, and I'd >manually set up the connector for IIS. This implies that you may have to get >someone to send you the connector DLL, or you may have to have IIS on the >server just to create the connector! Then, in WebSite Pro, I just associated >cfm files to the ISAPI connector, and created a content type for .cfm >mapped to wwwserver/isapi. I ran a test page with this code: > >#Server.ColdFusion.ProductVersion# > > >and it worked fine. So, WebSite Pro users (all three of you) rejoice! > >Dave Watts, CTO, Fig Leaf Software >http://www.figleaf.com/ >voice: (202) 797-5496 >fax: (202) 797-5444 > ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
