Posts Tagged 'Microsoft'

Microsoft Releases Office Translator for Office 2003 and 2007

The Microsoft Research Machine Translation (MSR-MT) Team today annouced they have released the new Office Translator plugin for Office 2003 and 2007.

I have yet to test out the tranlation capabilities, but when I do I’ll post here!

In the meantime go read the instructions on how to install it manually now, or wait for the Windows Update!

Read

Advertisements

Now This Is Cool – First Video of Microsoft Multi-Touch Sphere ‘Surfaces’

I first heard of this a few months ago when rumors of such a device first surfaced. Based on the same technology as the Surface multi-touch table, the Sphere allows users to interact with content on, well, basically a huge crystal ball. Cool. I’m especially a fan of the globe application and the 360° camera. The latter will be especially popular with security stations (imagine a 360° camera on the ceiling in the center of a room, and then the entire room being recreated on the Sphere.)

Check it out for yourself, more details to come as microsoft releases them.

[Via Engadget]

Tracing the Stack in SharePoint

As a SharePoint developer used to working with pure .Net, the first thing that I had to get adjusted to was SharePoint’s error handling and general debugging. Error messages, when they say anything other than a generic “error has occurred” message, are often irrelevant to the actual error that’s occurring.

Worse, the sharepoint logs are OVERLOADED with entries (I’ve seen SharePoint write over 100 log entries in a second) making it very very hard to find the entries that actually contain an error (this is why someone long ago invented the “log viewer”).

Add to that there is no switch in place in Central Administration to enable detailed errors, it instead requires manual modifications of the web.config file. So if you’d like to be able to see the stack trace of the error that is occurring, open the web.config file of your Central Administration site (or a different site if you so choose, located in C:\Inetpub\wwwroot\wss\VirtualDirectories\YourSitePort) and edit the following entries to turn off Custom Errors and enable the Call Stack:

<system.web>
    <customErrors mode="on" />
</system.web>

Should say…

<system.web>
    <customErrors mode="off" />
</system.web>

And

<SharePoint>
    <SafeMode MaxControls="50" CallStack="false" />
</SharePoint>
Should say…
<SharePoint>
    <SafeMode MaxControls="50" CallStack="true" />
</SharePoint>

If you are debugging a production system, you can instead set the “customErrors” mode to “remoteOnly”, this will allow the stack trace to be shown on the server’s browser, but not on any remote computers.

I guess we can chalk this lack of easy to use error handling on to the list of SharePoint “oversights” on Microsoft’s part (along with the lack of a x64 SDK, the SPTimer bug that often can’t queue more than 15 items correctly, and the fact that their paid SharePoint support line is usually unable to actually, you know, support anyone. At least we got our money back!)