NetworkedPlanet On Topic

EPiServer Module 3.3.0.37 has now been released. This update addresses an issue whereby registering events with SchemaJSON were not being fired correctly. Registering events with SchemaJSON now requires that after the event is registered FlushSchema() is called so that the event is properly registered.

EPiServer Module 3.3.0.36 has now been released.

• The topic map interface has been improved when dealing with topics scoped in multiple languages as well as for topics that are unscoped. Editors can now choose the language of topics they wish to see, either in a scoped language or all topics in their default unscoped view.


• Compatibility with Firefox has also been improved there may still be minor cosmetic issues however.

The upgrade requires that you install the EPiServer Module SQL extensions by running the included SQL script.

Today we have released a compatibility upgrade for the SharePoint Module extensions for the NPCL Schema Editor.

Due to some binary incompatibilities bewteen the Visual Studio SDKs for VS 2005 and VS 2008, the SharePoint Module Extensions for the NPCL Schema Editor that are provided with the current release of the SharePoint Module (SharePoint Module 3.1 Hotfix 1) do not load correctly when using Visual Studion 2008 and version 3.0 of the NPCL Schema Editor.

The new release is intended for use ONLY with version 3.0 of the NPCL Schema Editor in Visual Studio 2008 - for details and download please see this earlier posting.

The updated SharePoint Module Extensions can be downloaded from here. To install, simply copy the contents of the zip file into the Extensions directory as described in the documentation for the NPCL Schema Editor.

We are pleased to announce the release of version 3.0 of the NetworkedPlanet NPCL Schema Editor and NPCL Tools for Visual Studio.

The NPCL Schema Editor is a graphical editor that runs inside Visual Studio and provides developers with a drag-and-drop interface for creating topic map ontologies expressed in NetworkedPlanet's NPCL format, the format used by the EPiServer Module and SharePoint Module as well as other NetworkedPlanet tools.

The NPCL Tools for Visual Studio provides a bundle of new features to make it easier to work with NPCL files in Visual Studio. The current set of tools are:

• An MSBuild task for compiling multiple NPCL files into a single NPCL file for easy deployment;


• An MSBuild task for generating HTML documentation from an NPCL file;


• An NPCL Schema Editor extension that allows developers to add text and HTML documentation to the items in an NPCL schema;


• A Visual Studio project template for an NPCL Schema project that uses the MSBuild tasks to create a Visual Studio project for creating a large NPCL schema as a set of smaller, more easily managed NPCL files.

Most importantly of all, this new release is built on Visual Studio 2008.

As with previous releases, the NPCL Schema Editor and Tools for Visual Studio are provided free of charge and the latest version can be downloaded here.

A couple of customers have reported an error when starting up the Topic Map Index Service installed by the Enterprise Services 1.0 installer. When trying to start the service, the user will see a dialog displaying a message like:

"Could not start the TMCore Topic Map Index Service service on Local Computer
Error 1075: The dependency does not exist or has been marked for deletion"

What has happened is that the installer detected SQLServer installed on the machine and has inserted the dependency. The dependency it adds is against the normal SQLServer service name, but if you are running a different instance or are running SQLServer Express edition, you will need to modify that dependency.

WARNING: The fix to this problem involves changing registry keys. Please be very careful to change only the specified keys and ensure that you enter the correct values.

To fix this problem you need to first determine the name of the SQL Server Express service to add the dependency for. To do this, look for the server in the services list, then go to the Properties for the service. The service name is the value displayed as "Service Name" on the "General" tab of the Properties dialog. For example, on our own intranet server that uses SQL Server Express, the service name is "MSSQL$SQLEXPRESS".

Now go into the registry, go to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TopicMapIndex and change the DependsOnService value to the name of the database service that the topic map index service should wait for before starting up.

NOTE: If you don't actually connect to a database service on the same machine then just delete this value completely.