-
using the .Focus() method for a TextField throws a javascript error.
2009-07-14 20:11:25 UTC by mdkangas
-
The same problem. It was easier if you specified those command line options. Not really fast but i found them after all.
msiexec /i mod_aspdotnet-2.0.0.2006-setup.msi /qb INSTALLDIR="C:\web\bin\apache2_2"
/i - installs the package
/qb - no wizard ( use this option to be able to install, otherwise the same error will appear)
INSTALLDIR - directory where the apache instance is installed.
2009-06-10 10:47:59 UTC by nobody
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2009-04-30 02:20:07 UTC by sf-robot
-
This intersects with the GetClientCertificate interest, so researching.
2009-04-15 03:39:00 UTC by wrowe
-
For reference, this may be an allocation bug under the winnt mpm of httpd and not actually
related to .net, if you can confirm this was memory growth of the .NET vm and not the
process, that information would be useful to pursue this as an asp.net module flaw.
2009-04-15 03:37:55 UTC by wrowe
-
Still investigating which should be addn vs setn.
2009-04-15 03:36:25 UTC by wrowe
-
It only fails due to the depth of your directory and not naming the apache binary httpd.exe
(or perhaps using the 2.0 installer package). We search some 3 levels deep, we are not
looking for specific file-paths.
It can be overridden with options to MSIEXEC, leaving the incident as a note to remind me
to follow up on this documentation.
2009-04-15 03:33:38 UTC by wrowe
-
Wow, no, never encountered that before. You would have to reopen this bug with relevant
details, including the exact product family, version and service pack level of the OS and .NET
and which version of msiexec is installed. Perhaps also extract the log, the instructions for
troubleshooting are;
To help you any further, we need to see the error log. You can make one by using the...
2009-04-15 03:31:06 UTC by wrowe
-
Presuming this is a side effect of the fact that we flush-upon-completion and we don't actually
flush on each write. Usually small packets are not desireable, but this clearly calls for an
AspNet option flag to enable write-through. Looking into a patch for this, thanks for the pointer.
2009-04-15 03:27:28 UTC by wrowe
-
I agree, and mod_ssl exposes an API to help us implement. Will look at this implementation
in my (copious) free time :) Patches welcome, thanks for the suggestion.
2009-04-15 03:25:38 UTC by wrowe
