Destinator SDK 5 & Pocket PC in .NET

ado_civon · 05-09-2006, 09:58 AM

I hope someone can help out.

The PC version includes a DLL DestSDKLib.dll which can be nicely imported into C# or VB.NET in Visual Studio 2003. All works well.

Unfortunately such DestSDKLib.dll does not exist for the PPC version.

How do i get Destinator loading in Pocket PC using DestSDK.dll?
Has anyone tried this or got it working?

It would be great if someone could help me out, thank you in advance.

Ineffigy · 06-10-2006, 02:29 AM

You could try a process invoke. I never tried it though on a Compact Framework application though, I'm not sure if it will behave any differently.

TommyGun · 08-13-2006, 06:20 PM

Hi,

I've been working with the D3 SDK using interop in Visual Studio 2005 and VB.Net. I've now got the D5 SDK and would like to continue. The initialization is some what different - would you mind showing me the initialization code please. My target is also a PDA - so shortly I'll be going through the same issues - and will help out where I can.
TG

maartenclaes · 09-05-2006, 03:15 AM

Quote: Originally Posted by ado_civon

I hope someone can help out.

The PC version includes a DLL DestSDKLib.dll which can be nicely imported into C# or VB.NET in Visual Studio 2003. All works well.

Hello ado_civon,

I'm also trying to intergrate Destinator ND (v5) into a PC application. I'm using C# with dotnet 2.0. How did you get it working?

This is my test application:

Code:

using System;
using System.Collections.Generic;
using System.Drawing;
using System.Windows.Forms;
using DESTSDKLib;

namespace test2
{
	public partial class MainForm
	{
		Dest test = new DestClass();
		
		[STAThread]
		public static void Main(string[] args)
		{
			Application.EnableVisualStyles();
			Application.SetCompatibleTextRenderingDefault(false);
			Application.Run(new MainForm());
		}
		
		public MainForm()
		{
			InitializeComponent();
				
			test.ShowDestinatorWindow();
		}
	}
}

This is the exception I get @ "test.ShowDestinatorWindow();":

Code:

Exception System.InvalidCastException was thrown in debuggee:
Unable to cast COM object of type 'DESTSDKLib.DestClass' to interface type 'DESTSDKLib.IDest'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{F092A542-5F97-4AFD-886A-1B23A7F04BC8}' failed due to the following error: Bad variable type. (Exception from HRESULT: 0x80020008 (DISP_E_BADVARTYPE)).

I've tested this in SharpDevelop, Visual Basic 6 and Visual C# 2005 Express on my development PC and on a fresh installed Windows XP PC. All have the same issue.

Maybe the DestClass object need some more intialization? I've tested with the SDK version include in the latest CentraFuse. CF is written in dotnet 1 and Destinator ND is integrated into it. So it must be possible with the SDK they use.

CdRsKuLL · 09-05-2006, 04:04 AM

I believe the SDK that centrafuse uses has an extra hash key which is used here
res = g_Dest.CreateDestinatorWindow(F_DEFAULT,"KEY")

I think this is whats needed

CDR

maartenclaes · 09-06-2006, 01:29 AM

Ok, now I'm getting a messagebox "Wrong access key".

maartenclaes · 09-06-2006, 04:55 AM

The problem I had above (cannot cast ... to interface) can be passed by InvokeMember-calls to the COM object.

Code:

Type t = Type.GetTypeFromProgID("DestSDK.Dest");
obj = Activator.CreateInstance(t);

obj.GetType().InvokeMember("CreateDestinatorWindow", System.Reflection.BindingFlags.InvokeMethod, null, obj, new object[]{CREATE_DESTINATOR_FLAG.F_DEFAULT, "KEY"});

------------

obj.GetType().InvokeMember("ShowDestinatorWindow", System.Reflection.BindingFlags.InvokeMethod, null, obj, null);

------------

obj.GetType().InvokeMember("HideDestinatorWindow", System.Reflection.BindingFlags.InvokeMethod, null, obj, null);		

------------
	
obj.GetType().InvokeMember("DestroyDestinatorWindow", System.Reflection.BindingFlags.InvokeMethod, null, obj, null);

When I create the Dest object, a small unpainted window is created in the lefttop of the screen. When I call ShowDestinatorWindow, nothing happens. HideDestinatorWindow and DestroyDestinatorWindow removes the unpainted window. When I remove all maps from the destinator directory, I get a painted window which ask for a map. What am I doing wrong?

CdRsKuLL · 09-07-2006, 05:57 PM

your doing nothing wrong, the software is designed not to work unless you hold a valid key, this is only available from powerloc themselves.

CdR

Laidback · 10-25-2006, 05:43 PM

Anyone still working on this?

We can get past the 'key' message and I can get the map to show(and show my position etc.) but I haven't got all the extras yet.

For PC, I mean

gsova · 01-17-2007, 05:42 AM

Quote: Originally Posted by Laidback

Anyone still working on this?

We can get past the 'key' message and I can get the map to show(and show my position etc.) but I haven't got all the extras yet.

For PC, I mean

Laidback,

How did you get past the 'key' message? Have you patched the DestSDK.DLL?

I'm stuck with Dest 3 SDK...

Laidback · 01-17-2007, 12:27 PM

Now would I do such a dishonest thing like that?

And then tell you in plain view of the mods.....

gsova · 01-18-2007, 08:11 AM

I converted maartenclaes's code in VB.NET.

I have similar results. I can see that Destinator PN is starting through obj.GetType().InvokeMember and a box appears in the upper-left corner of the screen. I can also Show and Hide the box but no map appears inside the box. If I delete the maps from the ./DestinatorApps/Destinator folder I get the standard Dest PN map selection screen.

maartenclaes, I'm a beginner to .NET. Can you tell me how I could get/set a property for the COM object that is created with obj = Activator.CreateInstance(t) ?

Assuming that I wanted to modify or display the IDest.GPSProtocol Property, how would I have to call it?

gsova · 01-19-2007, 02:06 AM

One more thing to mention: If I remove Destinator.exe from the folder, when I initialize the Destinator Object, I get a message saying "my software is not correctly installed".

Isn't it strange that the DLL requires the EXE to work?

I'll try maartenclaes's code in C#

Laidback · 01-19-2007, 04:57 AM

'Strange' is the other name for the destinator sdk! :-)

Laidback · 01-21-2007, 05:53 AM

Quote: Originally Posted by gsova

One more thing to mention: If I remove Destinator.exe from the folder, when I initialize the Destinator Object, I get a message saying "my software is not correctly installed".

Isn't it strange that the DLL requires the EXE to work?

I'll try maartenclaes's code in C#

That message comes from destcore.dll