Posts Tagged ‘ Developement ’

CodePlex project for Word Automation Services

I’ve just published the first release for a CodePlex
project I started to provide sample projects / solutions for using the Word Automation
Services in SharePoint 2010.

Word Automation Services allow you to convert document to and from different formats.

File formats the service can read:

Office Open XML (DOCX, DOCM, DOTX, DOTM)

  • Word 97-2003 Document (DOC) and Word 97-2003 Template (DOT)
  • Rich Text Format (RTF)
  • Single File Web Page (MHTML)
  • HTML
  • Word 2003 XML
  • Word 2007/2010 XML

File formats the service can write:

  • PDF
  • XPS
  • Office Open XML (DOCX, DOCM)
  • Word 97-2003 Document (DOC)
  • Rich Text Format (RTF)
  • Single File Web Page (MHTML)
  • Word 2007/2010 XML

(source: http://blogs.msdn.com/microsoft_office_word/archive/2009/12/16/Word-Automation-Services_3A00_-What-It-Does.aspx)

As far as I’ve found out, there are no UI features available out-of-the-box to use
these services, so I’ve decided to create some. The first one is a custom workflow
action you can use in SharePoint Designer to convert a document to many of the supported
formats.

In the workflow designer you can add the “Convert Document” action:

here. He has included:



  • Sandboxed Visual Web Part Designer

  • SPMetal integration in Visual Studio for creating Linq to SharePoint proxys

  • Some Quck Deploy Steps in SharePoint Solution Deployment

  • Share/Bookmark

Tags:

January 8th, 2010  in SharePoint 2010 Beta, SharePoint Server 2010 No Comments »

Remove ‘init.js’ and ‘control.css’ from your public SharePoint site

Most of the SharePoint websites I work on do not expose any of the standard SharePoint functionality. They do not use webparts and so do not require any of the SharePoint javascript functionality.

SharePoint includes files to support the client side functionality of its controls, init.js, core.js, controls.css and core.css. These files are pretty large and in the interest of increasing the speed of loading your page its best to remove them, assuming they are not being used.

So a tip for your SharePoint publishing site is to remove them, but keep them available to your authors. You can do this using the AuthoringContainer control.

<PublishingWebControls:AuthoringContainer runat="server" id="AuthoringContainer1" DisplayAudience="AuthorsOnly">

    <SharePoint:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/~language/Core Styles/controls.css %>" runat="server"/>

    <SharePoint:ScriptLink name="init.js" runat="server"/>

    <Sharepoint:CssLink runat="server"/>

</PublishingWebControls:AuthoringContainer>

By wrapping these controls with a SharePoint AuthoringContainer you can speed up the load time of your publishing site to your visitors, but keep the authoring functionality available to your site authors.

Sometimes I have also included the PlaceHolderAdditionalPageHead to ensure other unwanted js or css files are excluded.

<asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server"/>

Another quick tip

Sometimes your custom CSS will not work well with the SharePoint field controls and so you need to fix the look and feel. This is important to make the editing experience as good as possible, ensuring the authors are happy. Personally I like to keep the default CSS specific to viewing the site and not try to have one CSS file for both viewing and authoring.

By using the SharePoint EditModePanel you can include a separate stylesheet, specifically designed to override any styles affecting the authoring look and feel. This makes the authoring experience much more usable, does not compromise your  original CSS and is only included when editing a page.

<PublishingWebControls:EditModePanel runat="server">

    <link type="text/css" rel="stylesheet" href="/Style Library/ARF_editing.css" />

</PublishingWebControls:EditModePanel>

  • Share/Bookmark

Tags:

December 3rd, 2009  in SharePoint 2010 Beta, SharePoint Server 2010 No Comments »

TextFlow Offers API, CompareMyDocs.com Web Service

TextFlow Offers API, CompareMyDocs.com Web ServiceIn May, Nordic River united productivity and collaboration with the release of the web-based version of TextFlow. This month, Nordic River has made its TextFlow Application Programming Interface (API) available.

Read full story…

  • Share/Bookmark

Tags:

November 10th, 2009  in SharePoint 2010 Beta, SharePoint Server 2010 No Comments »

SharePoint 2010 Developer Center

The SharePoint 2010 Developer Center is now live on MSDN. This new sub-site includes Getting Started modules, as well as a Beta version of the SharePoint 2010 SDK.

To read more, take a look at the SharePoint developer documentation team blog, or head straight to the SharePoint 2010 Developer Center to see detailed, public technical information and instruction around both SharePoint Foundation and SharePoint Server 2010.

  • Share/Bookmark

Tags:

November 7th, 2009  in SharePoint 2010 Beta, SharePoint Server 2010 No Comments »