Notices


Reply
 
LinkBack Thread Tools Display Modes

Old 04-16-2007, 05:26 AM   #1 (permalink)
Likes to customize RE!

DavidZ's Avatar

Join Date: Jul 2006
Location: London, UK
Posts: 335
Rep Power: 3 DavidZ is on a distinguished road

Blackbaud Products
- Raiser's Edge (RE)
- API/VBA

Using API and .NET with RE v7.71

I have to use the API with .NET on version 7.71 of Raiser's Edge. In 7.8 Blackbaud supplied the primary interop assembly folder (PIA) with the interop that you can use.

However for 7.71 there is no PIA supplied. There is a KB article about how to create one but looking at the MS site:

Calling COM Components from .NET Clients

When choosing whether you should reference the REAPI dll directly or build it yourself it says:

Quote:
If you did not write the COM component, neither one of these methods is acceptable. That's because you are not allowed to sign code written by another developer. What you need to do in that case is obtain a Primary Interop Assembly (PIA) from the original developer of the component.
The BB solutions (BB200505, BB121061, BB210789) do suggest that you create a signed key for the code so that it can be shared between different projects.

Does anyone know what the implications of this are? I have done this previously without a key and it seems to work but I am not certain what problems there would be if I did not create a key. Does this affect deployment?

Any help appreciated,

David
__________________
David Zeidman
Zeidman Development
http://www.zeidman.info

Check out my RE API blog
http://www.re-decoded.com


Last edited by DavidZ; 04-16-2007 at 05:34 AM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote

Old 04-16-2007, 08:32 AM   #2 (permalink)
Likes to customize RE!

DavidZ's Avatar

Join Date: Jul 2006
Location: London, UK
Posts: 335
Rep Power: 3 DavidZ is on a distinguished road

Blackbaud Products
- Raiser's Edge (RE)
- API/VBA

So I have found out some more information that probably answers my own question:

First the PIA is included with v7.71. I thought it only came with 7.8.

The reason why Microsoft says that you should not sign code written by another developer is because of compatibility issues. If you plan on using your application at another organisation for example and they have an interop assembly of the same name it will not be compatible. The PIA version takes precedence. This is why it is always advisable to use the manufacturers version. However normally when you build the interop yourself it is because you are doing so to use in your own organisation and do not have plans to share your applications with others.

As for signing the assembly, this is useful if you want to put the assembly in the GAC (Global Assembly Cache). This enables you to share your assembly - i.e. .NET version of Raiser's Edge API between applications. For more info about the GAC see. Demystifying the .NET Global Assembly Cache - The Code Project - .NET

Thanks for Ron Frum for some of the above information.

David
__________________
David Zeidman
Zeidman Development
http://www.zeidman.info

Check out my RE API blog
http://www.re-decoded.com

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
Reply

Tags
api, dotnet, interop, v771


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


Cheap Gas - Renegade motorhomes - Loan - Credit Counseling
All times are GMT -6. The time now is 03:39 AM.

Miscellaneous


Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Integrated by BBpixel Team 2008 :: jvbPlugin R1012.364.1

SEO by vBSEO 3.2.0 Copyright 2008 Blackbaud User SocietyAd Management by RedTyger
Inactive Reminders By Icora Web Design

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64