Mossquito client application requirements

To install Mossquito client application you'll need at least the following workstation or serversystem configuration:

• .NET Framework 3.5 (Service Pack 1 is recommended)
• One of the following Microsoft Windows operating systems:
  • Windows XP
  • Windows Vista
  • Windows 7
  • Windows Server 2003
  • Windows Server 2003 R2
  • Windows Server 2008
  • Windows Server 2008 R2
• At least 1 GB of RAM
• At least 1 GB of disk space for installation, data files, and log files

Mossquito server requirements

To install Mossquito Server application you'll need at least the following server system configuration:

• .NET Framework 3.5 (Service Pack 1 is recommended)
• One of the following Microsoft Windows operating systems:
  • Windows Server 2003
  • Windows Server 2003 R2
  • Windows Server 2008
  • Windows Server 2008 R2
• Either Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0
• At least 1 GB of RAM
• At least 1 GB of disk space for installation, and log files

When installing Mossquit Server you'll be prompted for a user account. The Mossquito Server service will run under this account, which needs administrative access to your SharePoint farm. Note that if your SharePoint installation has been installed as standalone and uses the Network Service account you can install Mossquito Server to run under this account.

Pre-deployment validation

Before deployment is performed, several validation checks are perfomed to make sure the data model is compatible with the target site. Mossquito checks if the site's web template matches the web template from which the data model originated. Similarly, Mossquito ensures that the target site has all features referenced by the data model activated.

DAO generator improvements

Enumeration types are now generated for Choice and Multi-Choice fields to further improve type safety of your code.

List GUID mapping is now supported by both the DAO generator and the Mossquito.Moss.ObjectModel redistributable assembly. When a data model is deployed using the “Generate new list GUIDs” option, generated DAO classes are able to match lists using their Internal Names and map these to the real GUIDs.

Improved UI experience

We've again paid more attention user interface. Besides many small improvements and fixes, enhancements like more organized context menus will help you achieve your work faster and more conveniently.

Improved performance

We have improved the overall performance of Mossquito resulting in a much more responsive UI.

Issues related to SharePoint integration

• When creating new views it is not possible to select a different view style on the Setup pane. As a workaround, modifying the StyleID property from the Properties pane is possible.
• Properties specific for views of type Calendar and Gantt chart are not available on the Setup pane. As a workaround, modifying the XML content of the ViewData property is possible.
• It is not yet possible to specify the order of list fields on new / edit / display screens.
• When you make a deployment, the target web site isn't locked for write access for the duration of the deployment yet.
• You may encounter specific differences after re-comparing a data model with live web site after deployment. However, these differences shall not have impact on the functionality of the target web site.
• Several list templates are not supported. Even though it's possible to use them in Mossquito, deployment isn't guaranteed to produce a working result. The affected list templates:
  • Data Sources
  • Slide library
  • Languages and Translators
  • Translation Management Library
  • Survery
  For all other list templates Mossquito shall deploy lists correctly, although you may still encounter minor differences between the model and the live state after deployment.

Features considered BETA

The following feature were included into this release of Mossquito but are provided for beta testing purposes mainly and as such may exhibit issues, known issues being described below.

• Merging of data models. Limitations and issues:
  • the feature requires that changes in both data models are accepted before the merge;
  • server-relative URLs in objects merged from a source data model aren't re-based by the target data model's own root server-relative URL;
  • when merging a live web site into a data model it's not yet possible to merge new list templates and field type definitions into the model;

• Navigation deployment — Mossquito isn't able to match navigation nodes from a live SharePoint web site against the model yet when doing updates to an existing web site.
• Navigation node ordering — you may sometimes experience unpredictable collapsing and expanding of nodes in the navigation tree editor when changing order of nodes using drag&drop or up/down options in the context menu. The changes made to the order of navigation nodes won't be deployed correctly to SharePoint yet.