Neno

Is there a sample showing how to add your own store (essentially write your own protocol handler) with .NET

(I am aware that there might be issues with different .NET Fx versions...)

Thanks,
Neno




Re: Windows Desktop Search Development Writing Protocol Handlers using Managed Code

Eric Wolz - MSFT

There are currently no .NET protocol handler samples. Right now, all shipping protocol handlers are native code. We understand the developer cuminity need for this and hopefully we can create some samples in this area.




Re: Windows Desktop Search Development Writing Protocol Handlers using Managed Code

Raffaele Rialdi

Neno, take a look here:
http://www.codeproject.com/aspnet/AspxProtocol.asp






Re: Windows Desktop Search Development Writing Protocol Handlers using Managed Code

Raffaele Rialdi

Maybe OT but I discovered this thread ...

I wrote my own protocol handler with C++ but when I use it inside a WPF object (like image) it only call ParseUrl for PARSE_SECURITY_URL and PARSE_SECURITY_DOMAIN and then stops (in IE it all works).

Is there any other particular Interface (beyond IInternetProtocol, IInternetProtocolRoot and IInternetProtocolInfo) I should implement in my protocol handler to be used in WPF

TIA






Re: Windows Desktop Search Development Writing Protocol Handlers using Managed Code

Eric Wolz - MSFT

That link is for writting protocol handlers for Internet Explorer and not WDS.




Re: Windows Desktop Search Development Writing Protocol Handlers using Managed Code

Igor Abade V. Leite - MVP

Eric, do you have any information about when (and if) we'll be able to develop WDS protocol handlers in managed code

Is it possible to write an out-of-proc protocol handler, in order to prevent the issue related to different .NET Fx versions loaded in the WDS process Or perhaps can WDS declare a preferred .NET Fx version to prevent conflict






Re: Windows Desktop Search Development Writing Protocol Handlers using Managed Code

Eric Wolz - MSFT

There is no current plans to recommend implementing .NET protocol handlers for WDS. There is no physical limitation that allows this, other than the standard .NET caveats, and people have written protocol handlers in managed code. Due to aggressive resource usage on .NET applications, it can impact indexing performance and may also impact user normal usage because larger memory requirements of the protocol host process to load your managed protocol handler. This is more apparent for machines running with minimal memory requirements (512-768MB). We do impose a max memory usage of protocol handlers to 100 Meg of memory.