Comments on: ASP.NET Web Services and STA COM Objects

By: Sam

Sam — Wed, 27 Aug 2008 21:40:39 +0000

ahhh – made a mistake above … can just use Context.Request.Path to get the actual virtual path … do no rigmarole of stripping the querystring

By: Sam

Sam — Wed, 27 Aug 2008 21:35:18 +0000

When I upgraded my site to 2008, I had to change the code as it gave a … is not a valid virtual path error.

The solution I found was to strip the querystring from the raw url:

override protected void OnInit(EventArgs e)
{
string virtualPath = Context.Request.RawUrl;
// strip the querystring off
if (virtualPath.IndexOf(’?') > 0)
{
virtualPath = virtualPath.Substring(0, virtualPath.IndexOf(’?'));
}

//Get the real handler and ask it to process the request
IHttpHandler Handler = defaultFactory.GetHandler(
Context
,Context.Request.HttpMethod
, virtualPath
,Context.Request.PhysicalPath);

if (Handler!=null)
Handler.ProcessRequest(Context);

}

By: roncansan

roncansan — Wed, 23 Jul 2008 19:39:22 +0000

I integrate this code to a project and it works fine when I’m debugging it under Visual studio development server, but when I move the code to a real IIS server 6.0, which by the way is in the same machine, I can not attach the ocx, myocx.attach() return -1. I know this a very general explanation, but I don’t know where to start. Any insight on this.

By: Danny

Danny — Mon, 14 Apr 2008 14:25:11 +0000

I found that I had to manually assign an arbitrary page id in the OnInit method, otherwise I got the following exception in EndProcessRequest:

Multiple controls with the same ID ‘__Page’ were found. Trace requires that controls have unique IDs.

[HttpException (0x80004005): Multiple controls with the same ID '__Page' were found. Trace requires that controls have unique IDs.]
System.Web.TraceContext.AddNewControl(String id, String parentId, String type, Int32 viewStateSize, Int32 controlStateSize) +475
System.Web.UI.Control.BuildProfileTree(String parentId, Boolean calcViewState) +359
System.Web.UI.Page.BuildPageProfileTree(Boolean enableViewState) +39

System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6341

By: Prafull Patil

Prafull Patil — Thu, 11 Oct 2007 22:38:05 +0000

Gr8. This idea is lifesaver although speed is not good but it is not bad too. Thank you very much.

By: Ben

Ben — Wed, 13 Jun 2007 06:23:13 +0000

I’ve implemented this handler, and have found that execution disappears into the COM call and doesn’t reappear for a very long time (long enough to cause the requesting app to give up with a webservice timeout). The COM object it’s calling is reasonably performant. Any ideas on what could be causing this?

By: Eyal Post

Eyal Post — Wed, 30 May 2007 11:57:04 +0000

Fixed. Thanks.

By: Sam

Sam — Wed, 30 May 2007 11:43:07 +0000

Got this working, but there is a typo:

The web services handler should be named WSHFactory instead of defaultFactory

Good work. Thanks

By: Ati Rosselet

Ati Rosselet — Mon, 05 Mar 2007 15:16:39 +0000

Hi, don’t know if you can help, but I’m dying with a certain STA component that requires AspCompat=true (in an aspx page). The whole webserver just blocks until the call completes.. and I can’t find a way around it. Specifically this is MS DRM-s WMRMObjs.Reheader object and within that, the Dowload function. Any ideas of how to circumvent this, or get it to unblock? Even if I cancel the download, I’m left with about 30s of deadtime until it finishes something internally ( This is a real project killer at the moment
My email is uramisten at hotmail dot com

Cheers

By: PR

PR — Fri, 20 Oct 2006 00:06:24 +0000

Never mind..I found it..
You can also use this with remoting.. You need to host your remoting server in IIS and instead of using WebServiceHandlerFactory, use RemotingHandlerFactory..
You can speicify this handler for .soap extensions in your web.config within section..