Web Developer Resources

What is Word Automation Services in SharePoint Server 2010?
Ever tried to transfer .docx files into PDF? Most of us try to perform server side conversions of Open XML files (.docx) into fixed formats (PDF and XPS) using the Word desktop application. Now this conversion can be done hassle-free with Word Automation Services.

As an element of SharePoint Server 2010, Word Automation Services allows you to perform file operations on the server that previously required automating desktop Word:
* Converting between documents formats (e.g. DOC to DOCX)
* Converting to fixed formats (e.g. PDF or XPS)
* Updating fields
* Importing “alternate format chunks”
Features of Word Automation Services

Features of Word Automation Services include the following:
o Reliability – Word Automation Service was built from the ground up to work in a server environment, which means that you no longer have to worry about issues like dialog boxes that bring the process to a halt, expecting a user to provide input; creating interactive user accounts under which to run the application to avoid running into permissions issues, etc.
o Speed – The service is optimized to perform server-side file operations, and in doing so provides performance significantly better than existing solutions.
o Scalability – The service can take advantage of the processing power available on typical server hardware (multiple processors, additional memory). For example, although a single instance of WINWORD.EXE can only utilize a single core of processing power, with Word Automation Services, you can specify the number of simultaneous conversions (and the # of processing cores) to use based on the available hardware.

What Word Automation Service doesn’t do in the SharePoint Server?
One of the most important things to understand about Word Automation service is what it doesn’t do. Word Automation Service is not intended to be a 1:1 replacement for the existing desktop object model. Instead, the server is one half of a replacement for the existing object model – the other half being the Open XML SDK.
o The SDK is designed to handle tasks that don’t require application logic, such as inserting or deleting content (paragraphs, tables, pictures), inserting data from other data sources, sanitizing content (removing content, accepting tracked changes), etc.
o The service is designed to handle those few tasks that do need application logic: reading the entire document formats that Word supports, converting to the entire output format that Word supports, recalculating dynamic fields, etc.

Word Automation Service is not featured in SharePoint Foundation 2010. Nevertheless, there is still life left in SharePoint family of products including Microsoft SharePoint Server 2007 and WSS 3.0 that has free SharePoint templates for business use.

I’ve been continuously saying that SharePoint Server 2010 and SharePoint Foundation has been launched with some really great features and when saying that I cannot afford to forget its yet another cool feature Developer Dashboard. The Developer Dashboard allows you to monitor page load performance on SharePoint. Simply put, you can see how each element on the page loads! Now isn’t that really cool?

The Developer Dashboard in SharePoint Server displays diagnostic information gathered during the loading and rendering of the SharePoint content. The dashboard, in conjunction with FireBug or the IE Developer Toolbar, helps developers and designers identify issues in their custom projects. This can be set to always display or to only display on demand. The Developer Dashboard has three different states—On, OnDemand, or Off. When the Dashboard is set to On, it will always be shown on every page. Read the rest of this entry »

There are different ways to organize data in a database. Utilizing Oracle or any other relational database there are advantages and disadvantages to these methods of relational database data organization .Depending on the business requirements and development needs, various ways of storing date can be implemented. The first data layout is horizontal. This is a traditional way of storing data in a table. Each new data record is inserted as a row and table columns run horizontally; hence, the name. The second method is vertical. This is a specific way of storing data vertically in a table that only has two real data columns and one other (but there could me more) identifier column. The data is stored as key/value pairs vertically; hence, the name.