I was just reminded that we were asked to document most of the changes that we took in SP2 so customers could get an idea of what was fixed and improved in the update. If you are familiar with open source this is similar to a chanelog and we now have this online, here is OneNote’s set of changes:
|OneNote||Before SP2, if you copied an embedded file and pasted it into other applications (Outlook, for example), it would only paste an image of the embedded file and not the embedded file. This bug fixes this problem. So, if you copy an embedded file from OneNote and paste it elsewhere, the embedded file will be there if the application in which you pasted supports embedded files.|
|OneNote||Before SP2, if you tried to create a shared notebook on SharePoint in a folder path where that folder and the parent folder didn’t exist, OneNote would fail. This bug fixes this problem. OneNote will ensure that the parent folder exists. If it does not exist, it will be created by the new notebook command.|
|OneNote||Before SP2, OneNote would sometimes fail to synchronize a section due to embedded files that had invalid file names according to SharePoint. For example, this issue occurred if the file name contained consecutive periods or contained a leading period. (For a full list, see the following Microsoft Knowledge Base article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;894629). When this issue occurred, OneNote gave the users an error message that told the users that they were not in sync but there was nothing for the user to do to get synchronization to work again. This bug fixes this issue. OneNote will filter out improper file names and make sure that they are valid before synchronizing to SharePoint.|
|OneNote||In certain cases, OneNote will continually try to ping a server to upload changes even though it has received an error that says that it could not upload the changes. This typically happens with read-only sections, and OneNote will keep trying to ping the server, which causes server performance issues. This bug fixes this problem. So, once OneNote receives the error, OneNote stops trying to synchronize.|
|OneNote||In certain situations, OneNote’s automatic background synchronization would not see that a section was deleted on the server and would still show the section in the UI.|
|OneNote||In OneNote 2007, many customers said that their OneNote Screen Clipper & Launcher, the OneNote taskbar notification icon, was missing and wasn’t appearing when they restarted their computers. This bug changes how this icon works; now when you choose to remove the icon, it will not disable the icon from running on the next restart. Before SP2, choosing that option would permanently remove the icon.|
|OneNote||SP2 fixes many synchronization performance issues with shared notebooks stored on SharePoint. This bug deals with how OneNote will send fewer HEAD requests for files in the notebook. This will help performance on the SharePoint server.|
|OneNote||When you synchronize a notebook on SharePoint, SharePoint might block some known file types. For example, SharePoint might block these file types: .asax, .ascx, .master, .skin, .browser, .sitemap, .config, .cs, .csproj, .vb, .vbproj, .webinfo, .licx, .resx, .resources, .mdb, .vjsproj, .java, .jsl, .lbd, .ad, .dd, .ldd, .sd, .cd, .adprototype, .lddprototype, .sdm, .sdmDocument, .mdf, .ldf, .exclude, and .refresh.
Before SP2, when a user tried to embed a file that had one of these extensions, a synchronization error would occur. Additionally, OneNote would not synchronize that section and would not give a meaningful error message. Now in SP2, when a user tries to embed one of these file types in a OneNote shared notebook on SharePoint, OneNote appends the .oneattachedfile extension to that embedded file and uploads it to SharePoint. To the user, it looks like the same file. On the server, there is an appended .oneattachedfile extension.
|OneNote||With SP2, we enabled image Optical Character Recognition (OCR) for the Japanese version.|
The OneNote 2007 SP2 list is short but should be considered the ‘gold standard’ that other Office development and documentation teams should follow. Instead of short and sometimes cryptic mentions that we’ve seen in other Service Pack 2 lists – the OneNote list is more detailed and useful to paying customers.
Yet again, OneNote leads the way – well done!
That just makes me happy since I wrote this stuff : )
Finally I wanted to mention something about our print driver, we still have the same problem that I mentioned earlier back when our September 2008 update came out. Again the same info applies so please check out that post for more details. We apologize for this, we tried to fix it in SP2 but were not successful, I think John might blog about this at some point so I won’t steal his thunder.