Chiming in. . .
The best way to integrate WebSphere Portal with .NET is via webservices, a
model based on well-thought out and well-supported standards. IBM has
examples of how a Websphere portlet can consume a webservice and emit potlet
UI. This is simple, and just works.
It is less optimal to integrate portal artifacts at the UI level. There is
a WSRP standard that attempts to cover this, but it is (IMO) neither well
thought out nor well-supported by either Websphere or .NET.
Architecturally, WSRP is an odd bird, and the implementation itself
introduces lots of challenges.
However, if you insist on pursuing WSRP, there are some technologies that
may help:
- NetUnity (
www.netunity.com) has a framework to enable WSRP-enabled
portlets in .NET. These are not Sharepoint artifacts, but NetUnity
portlets.
- There is a WSRP producer workspace on GotDotNet, not really usable in
production, but more a proof of concept. It's a Web service product that
ships a HTTP table (with all the right WSRP DHTML class taggin info) in a
WSRP-compliant SOAP envelope. Using this I think there is some manual
construction of HTML, which is then embedded in a WSRP envelope. NetUnity
does quite a bit more.
WSRP Toolkit for Sharepoint
http://www.gotdotnet.com/workspaces/workspace.aspx?id=805b3559-c810-4119-86f4-11ba5c16a5b0
-Dino