isapi

I found a WiX Tutorial , but it's really long-winded and seems like more than I wanted. What's the best way to get started quickly? My end goal is nothing really complicated: an installer that installs an ISAPI filter. I used that same tutorial a couple years ago when I needed to learn WiX. MSI (and therefore WiX) are incredibly complex, you'll need to invest some time to get it right. If you have Visual Studio, I highly recommend getting Votive (which, I think, comes bundled in WiX v3 now). It'll set up VS to recognize the WiX XML schema and make hand-editing XML files much easier. When you

I'm serving a Django app behind IIS6 web server. The test server runs perfectly, but when running behind the web server a module failes to import I get this error: Error loading pyodbc module: DLL load failed: The specified module could not be found Just for the record the module is pyodbc The site is served though isapi by using isapi-wsgi Any ideas? It would really make my day! :) This error is a PITA: it is often caused by missing symbols in dll (because a dependent dll was not found, etc...). You should check the .pyd with dependency walker, or look into the windows log which may log such

what are minimal steps required to make ISAPI dll working in IIS7 for query www.website.com/test/bin/ISAPIGet.dll?a=b ? Please don't refer to top google searches, they are very generic and don't work. I wrote very simple ISAPIGet.dll in Delphi2010, which works great in IIS5 Win2000. Then I put it on IIS7 SBS2008, into C:\inetpub\wwwroot\website\test\bin folder. Created website for /website, Application for /test, VirtualDirectory for /bin, in HandlerMappings for /bin Added Script Map *.dll to my ISAPIGet.dll, allowed my dll in ISAPIandCgiRestrictions, created 32bit ApplicationPool NonManaged

I'm converting a Delphi ISAPI dll to work better on IIS 7.0 and 7.5. The ISAPI used to read its configuration from the registry but I wanted to convert that to using the web.config file in the same folder. It worked fine with CGI but the ISAPI is another matter. I'm using GetModuleFileName to get the path of the module and, of course, it's giving me back the path of the IIS worker process (C:\Windows\SysWOW64\inetsrv). Is there a way to get the physical path of the ISAPI dll itself ? RBA I'm using this function and works great. function GetDllName: string; var pName: PChar; begin GetMem(pName,

So, the site I'm working on is using urlrewriting in coordination with aspnet_isapi.dll (everything is mapped to it). I put up my app_offline.htm file, and all the text shows, however, the CSS or images aren't being served. I'm guessing they're being processed by ASP.NET due to the wildcard mapping instead of IIS. Is this correct? If so, how can I allow IIS to serve these files? Furthermore, an issue I can see arising..in the web.config for the rewriter settings: <rewrite url="^~/images/network/(.*)/(.*).jpg$" to="~/services/ImageHandler.ashx?type=$1&id=$2"/> <rewrite url="^~/image/view/(.*)

So IIS7 in Integrated Pipeline mode uses a IsapiFilterModule to shim ISAPI filter DLL's and fire off the correct "events" on the filters, which is quite different than previous versions of IIS or IIS7 in classic mode because this means that HttpModules fire off right along side ISAPI filters in Integrated Pipeline mode. So does anyone happen to know how ISAPI events ( http://msdn.microsoft.com/en-us/library/ms524855.aspx ) and the HttpModule events ( http://msdn.microsoft.com/en-us/library/ms998536.aspx ) line up? VMAtm HttpModule events are fired after other filters, according to the MSDN: At