Since the release of Squiggle 1.0, we’ve received plenty of feedback and feature requests. Newer version has one of the most demanding features “File Transfer”. Squiggle can now help you exchange documents with your colleagues.
You can download the latest version of Squiggle from http://squiggle.codeplex.com/
Overroot is pleased to announce the release of yet another product “Squiggle”. Squiggle is a free LAN messenger designed for instant messaging within small and medium offices. Squiggle, having a simple and intuitive user interface, is an easy to use LAN chat solution for your LAN or a private network. It is based on peer-to-peer technology and requires no dedicated server or an internet connection.
You can download Squiggle from http://squiggle.codeplex.com/
Following are the key features of Squiggle.
If you have any suggestions, comments or you’re willing to participate in this open source project, then please send us an email at info [at] overroot [dot] com
Event logging is a standard way for applications to record important events. Most of the windows applications log their messages, warnings and errors in event log.
Microsoft SharePoint Server, although, has it’s own centralized logging mechanism but it does not log it’s messages to event log. SharePoint LogViewer has a new feature in it’s most recent version (v2.5) to record all or few of the events in window’s event log. You can select the minimum SharePoint severity level from which the logs should be reported to event log.
In SPLV, we used System.Diagnostics.EventLog class to write messages to event log.
Following is the C# code to write log entries to event log.
string source = "Demo Application"; if (!EventLog.SourceExists(source)) EventLog.CreateEventSource(source, "Application"); EventLog.WriteEntry(source, "Message!", EventLogEntryType.Error);
Although, these lines of code work fine, it, however, requires the application to run under the administrator’s account otherwise it may throw a System.Security.SecurityException.
To have this feature working in SPLV, we recommend it’s users to run SPLV under the administrative privileges.
With SharePoint 2010 on the verge of it’s release, it is very important to make your existing SharePoint applications compatible with it. SharePoint LogViewer was initially built for viewing SharePoint 2007 logs but it still could be used to view SharePoint 2010 logs until one of the most powerful feature ‘Live Monitoring’ was introduced.
‘Live Monitoring’ requires you to run SPLV on machines where SharePoint is installed. Earlier it was only able to detect SharePoint 2007 while SharePoint 2010 logs could not be monitored. SPLV detects the SharePoint installation by reading registry keys. To find the SharePoint location on a machine, SPLV used to read a registry entry ‘Location’ under the path
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0.
But this only worked for SharePoint 2007 as SharePoint 2010 has a different registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0.
Now SPLV tries to locate any of the above mentioned two registry keys to detect SharePoint installation which makes it possible to monitor Live logs for both SharePoint 2007 as well as SharePoint 2010.
For those of you who want to deploy their SharePoint 2007 solutions on SharePoint 2010, Andri Yadi’s article SharePoint 2010 Solution Installer may help.
Download the latest version of SPLV from here
