After some investigation I found a component online which is completely .NET based with royalty free distribution. The component is Cablib by WoutWare. The API is simple and easy to use but provides all the power that is needed for this project.

They are not editable though, and therefore need to be removed from any candidate editable feature classes you may be looking at.

The following piece of code can be used to determine if the ftrClass is editable:

ICompressionInfo info = featureClass.FullName as ICompressionInfo;

if (info != null)

{

    if (info.IsCompressed == true)

        return true;

}

To allow for complete control of the application configuration, GO! Sync Mapbook uses reflection to load all of it’s components. This seems to cause a problem in Vista with machines that have Data Execution Prevention (DEP) running. The ActiveX controls that makeup ArcGIS Engine do not load properly.

There is a pretty good article here that shows how to turn it off completely.

I used the following command line to fix it:

bcdedit /set nx AlwaysOff

You need to run the command prompt as Administrator for it to work.

Luckily, ESRI have a great EDN post about it which explains everything.

Essentially, you do not populate the IPropertySet with the USER and PASSWORD values but rather set the AUTHENTICATION_MODE to OSA.

The rest of the connection parameters are the same and since we normally use connection files in our applications it means that the connection file just needs to be changed.

GEOPRESS_LOCATION(Home)

One problem though. I am using Filebased Geodatabase and I did not know what the correct way to encode the date is! I thought about it for a little while and then decided to use the trusty Query Builder from within ArcMap. It worked a charm.

It is hard to see but they encode the date by pre-pending ‘date ‘ and encoding the actual date in ‘yyyy-mm-dd’ format.

Must archive this somewhere in my brain where it will not get lost!

• 64-bit Windows
• ArcGIS 9.2
• .NET 2.0

at the same time. When trying to initialize AO using the following code

IAoInitialize init = new AoInitializeClass();

it fails with an error like this:

System.Runtime.InteropServices.COMException
Retrieving the COM class factory for component with CLSID {2237A429-E4AC-40D6-96A5-5B6CCF40D56B} failed due to the following error: 80040154.

We did some digging and, thankfully, someone has already figured it out. It turns out that if you build any .NET code with the ‘Any CPU’ option which is the default then ArcObjects based applications fail. This makes sense as the c++ dlls that are built for AO are 32-bit so the application/assemblies that are consuming them also need to be 32-bit.

Fixing the problem is pretty easy (although if you have a bunch of assemblies like we do tedious!).

First thing to do is select ‘Configuration Manager’ from the  Solution Platforms drop down (the one with ‘Any CPU right now’):

It actually brings up the same configuration window as the Debug/Release configuration!

From the ‘Active solution platforms’ drop-down select ‘New’:

and from the resultant ‘New Solution Platform’ select x86. This is create a new configuration for x86 only. This way when it is run on a 64-bit environment the OS will know that it should be run as a 32-bit application.