> Anyhow, I guess the main problem will be figuring out what to
> do about the extra
> "Web Services Extension" tab in IIS 6. Strangely I think that
> filters work
> without extra complication, but an extension needs an extra
> step ie entering and
> enabling in the WSE list.
Can you please try wi
Mark Hammond wrote:
>..
> This was due to IIS6 providing "unlimited length style" filenames (eg,
> "\\?\c:\etc") I've recently fixed that in the source here so will be fixed
> in the next release. In the mean time, you may want to check your
> sys.path[0] entry - it is likely to also be a pat
> what I try I cannot get the page to say anything other than
> "This module has
> been imported 0 times". removeing the pyc's and or editing
> the .py seemed to
> have no effect.
This was due to IIS6 providing "unlimited length style" filenames (eg,
"\\?\c:\etc") I've recently fixed that in the
David Primmer wrote:
> Robin Becker wrote:
>> Robin Becker wrote:
>>> I thought I'd check here in case anyone has already connected django to IIS.
>> despite this it seems that the application produces a page. However, no
>> matter
>> what I try I cannot get the page to say anything other than "T
Robin Becker wrote:
> Robin Becker wrote:
>> I thought I'd check here in case anyone has already connected django to IIS.
>
> despite this it seems that the application produces a page. However, no
> matter
> what I try I cannot get the page to say anything other than "This module has
> been im
Robin Becker wrote:
> I thought I'd check here in case anyone has already connected django to IIS.
>
>
Well I thought I'd give the isapi module a twirl as it seemed it would be easy,
but with IIS 6 running on a virtual Win Server 2003 Web edition I fell at the
first hurdle. The hosted environ
