Worksite.dll Class not registered using .Net v2

I've been using the SDK for some time with v1.1 of the .Net framework and Visual Studio 2003 no problem, and the following code works fine in it, however, I can't get this code to work with Visual Studio 2005 and v2 of the framework:
Try
Dim m As IManage.ManDMS = New IManage.ManDMS
Dim s As IManage.IManSession = m.Sessions.Add("WORKSITE")
s.TrustedLogin()

MsgBox(s.UserID)

s.Logout()
Catch ex As Exception
MsgBox(ex.Message)
End Try

The error is:
"Retrieving the COM class factory for component with CLSID {FDD9199A-1BB4-4433-B9E1-D550D3118676} failed due to the following error: 80040154."

Can you help? I wondered is there was something special you had to do to get reference the Worksite.dll in Visual Studio 2005?

Thanks
Gary

Edited by garymccl on 11/14/05 03:48 AM (server time).

Find more posts tagged with

Comments

jny

Could you attach a simplified, reproducible project?

garymccl

I cannot produce a ZIP file with the project in small enough to upload.

Can I email it to you?

Thanks
Gary

jny

Sure. E-mail it to devnet-team@interwoven.com and mention jny as the recipient and someone will forward it to me.

Thanks.

jny

Gary,

If you are still having trouble with this and looking for help, and have the WorkSite iToolkit, you should seek support by sending your code to worksite-devsupport@interwoven.com so that a ticket can be opened for you by the automated incident tracking system. Please keep in mind that they only accept a simplified version of your code. Since you already know exactly where the error hits, you should be able to strip it down and add it to a simple project to send it in...any unrelated code in a huge project will either get rejected thus the turn-around time might take longer.

On a separate note, if you have successfully referenced the DLL's in 2003, it should also work the same way in 2005. Make sure it's not something related to how you have updgraded the VS .NET environment.

Please keep in mind that this is a forum and not a support channel thus this might not be an appropriate place to accomodate an issue of urgent nature.

Thanks.

Migrateduser

Are there any known issues/caveats/differences/etc. with moving to Visual Studio 2005?

jny

I learned from Gary that a problem occurs when using Windows XP 64bit Edition (the 64bit edition of .Net Framework v2 and Visual Studio 2005) to reference a 32bit DLL (such as Imanage.dll) from a VS2005 application. In such case, the target CPU (in the Advanced Compile Options) needs to be set to “x86”.