Question

In the company I work for we have a desktop application developed in .NET that we like to open up some parts for other software developers.

I see it like some kind of public methods that other software can access. Is there any standard approach, best practices or other experience of this?

I guess you could do this with Win32 calls, C/C++ programming etc. But I’m mainly a .NET developer and have some years of experience programmming in mainly VB.NET but also some C#. I hope finding a way to do this within .NET. But it should be accessible for software developed in other languages.

Best regards/ Magnus

Answer 1

There are two ways to go about this. The first involves using the Plug In / Module pattern. Start here for that.

A second way is to simply expose your API logic through well documented assemblies.

The way you pick really boils down to how you want it implemented. For example, Adobe Photoshop uses the plug-in pattern to great extent. MS Office uses both plug-ins as well as provides an object interface for working with the application.

UPDATE: Objects in .Net assemblies can be exposed to be consumed by external applications simply by setting the objects scope to Public. This includes windows forms, business objects, enum’s, etc.

Just think about it from the external developer’s perspective. What information will they need to have in order to be successful at extending / controlling your product? Whatever that is, put it in the help file.

Also, make use of the auto-documentation features of .Net. This includes adding xml documentation the the IDE already knows how to read and display via intellisense. For example:

/// <summary> /// Gets all active documents for the specified customer. /// </summary> /// <param name='customerId'>The Id of the customer.</param> /// <returns>A list of documents for this customer.</returns> public static List<Document> GetDocuments(int customerId) {     //... do something ... }