WorkSite 8.0 SDK

What is the real difference between the SDK for 8.0 and earlier versions? Does this statement from the press release hold true:

"Intranets, Extranets, and Support for .NET. WorkSite
8.0 uses the Microsoft .NET framework, C# and ASP.NET for Web
applications to provide a next-generation platform for seamless intranet
and extranet creation; the WorkSite SDK is also now fully .NET
compliant. With this move to .NET, Interwoven WorkSite users can expose
Web services for workspace creation."

Is it fair to say that the key DLLs have been cleaned up to allow simpler and reliable COM Interop usage?

Best Regards,
David

Find more posts tagged with

Comments

Migrateduser

There's a webcast recording on DevNet that talks about new features in WS 8. Check out:
http://devnet.interwoven.com/site.fcgi/webcasts/docs/webcast-recordings.html#webcast04-11

Regards,

lissa

jny

Currently, our COM type libraries are not developed and compiled in the .NET environment thus .NET will treat it as unmanaged code. This, however,
will not keep you from making calls to our COM API in .NET using languages such as C# or VB .NET.

There is no cleaning up involved.

dmdejong

I was aware that it is unmanaged code but I assume that doing the same thing from .NET with the 7.5 SDK would not be nearly as 'clean.' Does ".NET Compliant" just refer to the way function parameters are passed in/out of the COM library?

Also, is it possible to download the 8.0 SDK documentation somewhere while I await a licensed copy?

jny

Currenlty, the way to consume 8.0 COM Object Model in .NET is the same as before 8.0:

- Add reference to a registered 8.0 imanage.dll.
- Add directives:
using System.Runtime.InteropServices;
using IManage;

As far as I know, the SDK documentation manuals are only distributed with the purchase of the Worksite iToolkit, as it's a very integral part of the SDK.

RussWilmott

I've started using SDK 8.0 with .NET by referencing the c:\Program Files\Interwoven\Worksite\iManage.dll which produces the interop.imanage object in my project.

However, there is an SDK80SAMPLEAPP in C# which comes with a different dll called Interop.iManage.dll which also produces the interop.imanage object in the project but is different from the iManage.dll object in that it has moved all the objects into imanage.worksite. So the 2 different structures are as below. Why has this been done?

IMANAGE.DLL :-

- Interop.IManage
- IManage
- AccessRight
- ACLType
- etc.

INTEROP.IMANAGE.DLL :-

- Interop.IManage
- IManage (is blank)
- IManage.WorkSite
- AccessRight
- ACLType
- etc.

jny

At the time of developing the application, the sample application code developers share the same DLL that our Worksite Web code was referencing as they were able to always get to the latest build during the course of their development so they simply took advantage of this internal source; hence the namespace was 'Using iManage.WorkSite' as this is the namespace of Worksite Web application'.

In the sample form code, SDK80SampleApp.Form1.cs, you should see this in the Using namespace area:

//using IManage;
//-- use this namespace to reference the iManage.dll that is registered on your machine.
//--- this should be declared in every .cs file that you have.

Please follow this instruction to use your own copy of the DLL, and comment out iManage.WorkSite;

Edited by jny on 08/02/04 01:57 PM (server time).

abc1234

from where i can get this sdk