The new SP5 release of TMCore07 fixes a packaging issue found with the SP4 release that may prevent the faceted search features of the TMCore SharePoint Module from working correctly. Customers having a current support contract or currently evaluating TMCore may receive TMCore07 SP5 free of charge.

For download details please email us at contact@networkedplanet.com.

-------------------------------------------------------------------
-- tm_displayName
-- Returns a display string for a topic selected from the topics variant names and topic names.
-- Since: 1.0
-- Last Updated: 2.4
if exists (select * from sysobjects
where id = object_id(N'[tm_displayName]') and
xtype in(N'FN',N'IF',N'TF'))
DROP FUNCTION [tm_displayName]
go
CREATE FUNCTION dbo.tm_displayName (@topic int)
RETURNS nvarchar(512)  AS
BEGIN
DECLARE @disp int
DECLARE @ret nvarchar(512)
SELECT @disp = (SELECT TOP 1 topic_id from tm_si
WHERE
tm_si.topicmap = (select topicmapref from topic where id = @topic) and
subj_id='http://www.topicmaps.org/xtm/1.0/core.xtm#display')
SET @ret = (SELECT TOP 1 variant_value FROM tm_nameVariantValue JOIN tm_variantScope ON tm_nameVariantValue.variant_id = tm_variantScope.variant_id
WHERE
tm_nameVariantValue.topic_id = @topic AND tm_variantScope.scoping_topic_id = @disp
ORDER BY tm_nameVariantValue.variant_id ASC)
IF (@ret IS NULL)
SET @ret = (SELECT TOP 1 name_value FROM tm_nameValue JOIN tm_nameScope ON tm_nameValue.name_id = tm_nameScope.name_id
WHERE
tm_nameValue.topic_id = @topic AND tm_nameScope.scoping_topic_id = @disp
ORDER BY tm_nameValue.name_id ASC)
IF (@ret IS NULL)
SET @ret = (SELECT TOP 1 name_value FROM tm_nameValue JOIN tm_nameScope ON tm_nameValue.name_id = tm_nameScope.name_id
WHERE
tm_nameValue.topic_id = @topic and ((tm_nameScope.scoping_topic_id IS NULL)  or (tm_nameScope.scoping_topic_id = -1))
ORDER BY tm_nameVALUE.name_id ASC)
IF (@ret IS NULL)
SET @ret = (SELECT TOP 1 name_value FROM tm_nameValue WHERE tm_nameValue.topic_id = @topic ORDER BY tm_nameValue.name_id)
RETURN @ret
END
GO
grant exec on tm_displayName to tm_reader, tm_writer
go

• 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.

• BUGFIX: Fixed extension loading code so that a copy of the NetworkedPlanet.Npcl.Vs.Dsl.DLL is no
  longer required in the extensions directory. If you previously added this file to the
  extensions directory to fix extension loading issues you should now delete that file.
• NEW: The installer now includes policy files so that extensions that targeted version 2.0.0.0
  or version 2.0.0.1 of the NPCL Schema Editor will continue to work after an upgrade.
• NEW: Added README and INSTALL text files to the release package.

The sharp-eyed among you will have noticed that we haven't yet upgraded this package to work with Visual Studio 2008. This is the next thing on the list and will be part of the forthcoming 2.1 release of the schema editor.
You can download the new NPCL Schema Editor from here. Please note that if you have a previous version of the schema editor installed you must uninstall that before attempting to install the new version.
I also found a couple of minor annoyances in the SharePoint Module extensions for the Schema Editor and fixed those. The updated extension package can be downloaded from here.
As usual if you have any comments or suggestions for improvements or, dare I say it, bug reports please send them to support@networkedplanet.com.

TMCore07 SP3 Known Issues, Fixes and Workarounds

This blog entry is used to record and document known issues found with TMCore07
SP3 edition and their current status.

If you discover an issue with TMCore07 SP3 that is not listed here, then please
report it to us at support@networkedplanet.com.

If you've used TMEditor on Windows 2003 you may have experienced the following error when using TMEditor:

There are several reasons why this may happen; however there is a general way around this problem which is to disable ViewState MAC validation. To do this edit the TMEditor's web.config file and add the following as a child of the system.web section:

<pages enableEventValidation="false" viewStateEncryptionMode="Never" enableViewStateMac="false" />

However please note that this may allow attacks on the application or IIS on a public-facing server; however if you've got TMEditor sitting unprotected on an internet connection then you're already in trouble .

The following references provide more information:

• http://forums.asp.net/t/955145.aspx?PageIndex=9 - ASP.NET forum post
• http://msdn2.microsoft.com/en-us/library/aa302426.aspx - Building Secure ASP.NET Pages and Controls (MSDN).

Microsoft SQL Server 2005 Express Edition (henceforth MSSQLEE) that is free to download, use and embed. You can download it from Microsoft here.

Once you have downloaded MSQLEE, you'll notice very quickly that this is definitely not the same as regular SQL Server. Most immediately noticable are the lack of the Enterprise Manager and Query Analyzer tools. Fortunately Microsoft have made available, as a separate download, SQL Server 2005 Management Studio Express, also this article, Managing SQL Server Express with SQL Server 2005 Management Studio Express Editon, may give you some useful insights in how to use this utility.

Once you've downloaded and installed these, the next steps are to:

1. Create the topicmap database, using Studio Express.
2. Use Studio Express to load the database schema, tmcore.sql, in to the database. See note below.

Note: When you execute tmcore.sql against the database you will see the following output:

(1 row(s) affected)
(1 row(s) affected)
Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.

This is a known issue which does not cause any problems with the operation of TMCore (you will see the same message when using the non-express edition of SQL Server 2005.

If using MS SQL Server this would be the end of configuration, however for MSSQLEE you will hit errors errors fairly quickly. If you try to use TMEditor or TMWS you will most likely encounter the following error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

By default MSSQLEE does not accept remote connections. To enable this, you can use the SQL Server Surface Area Configuration utility to set MSSQLEE to be Using both TCP/IP and named pipes under the Database Engine -> Remote Connections sections. You may also need to enable SQL Server Browsing and open the firewall to accept connections on the required TCP/UDP ports. See this Microsoft Knowledge Base Article KB914277 for a full description on how to do this.

Finally, the connection string in TMEditor and TMWS's web.config files will need updating to use a form that MSSQLEE will understand and tolerate. It will be something in this form:

<add key="networkedplanet.tmcore.dbconnect" value="Data Source=SERVER NAME;Integrated Security=SSPI; Initial Catalog=topicmap" />

Where servername is of the form: machine name\service name. Therefore if your host name is DEMETER, and you're using the default service name of SQLEXPRESS, you full connection string will be:

<add key="networkedplanet.tmcore.dbconnect" value="Data Source=DEMETER\SQLEXPRESS;Integrated Security=SSPI; Initial Catalog=topicmap" />

Once these steps are followed, and replicated for your own applications, you should find that SQL Server Express provides a quick and convenient way to use TMCore.

If you'd like to add your own hints and tips for using MSSQLEE then please comment below. If you encounter any problems with this guide or you think we should add some more information, then please e-mail us at contact@networkedplanet.com.

<system.web>
<webServices>
<protocols>
<add name="HttpPost"/>
</protocols>
</webServices>
</system.web>

If using ASP.NET 2.0 you can apply this configuration change to only the path containing the web service by wrapping the above XML in a location element:

<location path="NetworkedPlanet/EPiServerModule/Service">
<system.web>
<webServices>
<protocols>
<add name="HttpPost"/>
</protocols>
</webServices>
</system.web>
</location>