Manual Deployment of Visual Studio Add-Ins

May 16, 2008

To deploy visual studio addin you have to place the AddIn file in this directory:

My Documents\Visual Studio 2005\Addins\

Open the AddIn file. You will see XML seems the following:

<?xml version=”1.0″ encoding=”UTF-16″ standalone=”no”?>
<Extensibility xmlns=””&gt;
<Name>Microsoft Visual Studio</Name>
<FriendlyName>Sample Addin</FriendlyName>
<Description>Sample Addin Description</Description>

Change the Assembly value to be the path of your addin DLL.

Change the full class name to be (<YourClassName>.Connect)

Then you will be ready to see your addin in the visual studio


Localization in SharePoint ASPX Pages

May 16, 2008

To add a text from a resource file into your SharePoint ASPX page you have to place this code where ever you want this text to places.

<%$Resources:MyResource, MyName%>


– MyResource: is the resource file name.

-MyName: is the resource entry key.

Your resource files must be placed in this directory:


all resource files in this directory are copied to the global resources for every web application when it’s creating.

if the webapplication already exists place the resources files in this directory:


where <port> is the the web application port

SharePoint Content Deployment and Migration API

May 16, 2008
  • Using deployment and migration APIs contents may sync between different sites using deployment packages these packages may be translated before they uploaded to the target site.
  • Its move all of the list related data (permissions, pages, web Parts,…).
  • It’s Very strong if we talk about the way it gets the relative data for very item.
  • Reserve ID or create new one.
  • Supports incremental deployment. So, it can deploy new changes only.
  • Limitations:
    • Incremental export/import is supported only in the site scope.
    • In the lists the old items will not be overwritten they will duplicated. But in case of document libraries: the old items overwritten.
    • Unexpected behavior when using to transfer list from a variation site to another variation site have the same list.
    • Can’t export items from different site collections in the same operation.

My SharePoint Variations Notes

May 16, 2008
  • Features:
    • Building multilingual sites by building a site (called Label) for every language and transferring the changes from source language site to all other sites.
    • Redirecting the user to the site matching the browser language.
    • Placing a control to change the language in the top navigation bar.
    • A service is running every 20 min to propagate changes from the source language site to all other sites.
  • Limitations:
    • Transferring changes from the source language to others. So changes in any language other than the source are not reflected in other sites.
    • Pushing a new version from a page to all sites even if there is a minor change like spelling mistake.
    • One to one relationship with site collection (one variation per site collection).
    • Lists changes are transfer only when it’s contained in a new site created.
    • When creating sites using features the target sites created without localization.
    • The localization is working only when creating new sub site and the label sites.
    • List view web part references the source site list in every site it is propagated to(because it use the list ID).
    • Variation fails when trying to push a page when there is a page with the same name but with different content type in the destination site.
    • Permissions are not propagated.
    • Works only on publishing pages.
    • Can’t change default page layout.
    • Don’t support site restore.
    • Variation sites must be in the same level and their parent site must be the root of the variation.
  • Risks (from blogs):
    • Sometimes variations cause performance issues.
    • May cause an expected behavior with heavy look and feel customizations.
  • Variations in other Blogs:

Multilingual System Design: (3)Data Layer (Stored Procedures)

May 16, 2008

In this post, I will discuss the logic contained in the data layer. The data layer logic is all in stored procedures and functions.

First, Let us discuss the logic for the Languages table. The following stored procedures may be defined on the languages table:

  • AddLanguage: Add new language to the system. You must take care that this stored procedure not only adds a record in the languages table but it also adds a record for that language into all child tables.
  • DeleteLanguage: Delete language from the system. You need to remove all the records related to that language from child tables. You have to check also if it’s the default language for any user then he/she has to change it.
  • UpdateLanguage: Update the details for a language.
  • GetLanguageDetailsById: Retrieves all the language data using language ID.
  • GetAllLanguages: Retrieves all the languages supported by the system.

Then we can define a group of stored procedures on every multilingual parent-child tables:

  • AddRecord: This stored procedure is defined on the parent child records. It first adds a record in the parent table then adds its child record for a specific language and adds empty child record for each other languages. This stored procedure may use two other stored procedures or functions:
    • AddParentRecord.
    • AddChildRecord.
  • UpdateRecord: Updates a parent record and one of its related child so it needs to take a language parameter. Also, it needs another two stored procedures:
    • UpdateParentRecord.
    • UpdateChildRecord.
  • DeleteRecord: Deletes a record from parent table and all of its related child records. Again, it needs the two stored procedures:
    • DeleteParentRecord.
    • DeleteChildRecord.
  • GetRecoredByLang: Retrieves the parent record and one of its children defined using the language paramenter.
  • GetAllRecoreds: Retrieves the parent record and all of its children.

After developing these procedures for all tables, you need to move to the data access layer. In this layer, you have to make functions that allows you to connect to the database and access your tables and stored procedures. It’s so basic and straight forward so I will skip it.

Next time, I will talk about the business logic.

Multilingual System Design: (2)Data Layer (data structures)

May 15, 2008

After taking a look on the system, in this post I will describe the suggested design for the Data Layer.

In the data layer we need to have a place to store the languages included in the system. This design support dynamic number of languages even while the system is running. So, a table to store the languages is needed.

In this table we have the Language ID (LangID) that stored a number uniquely indentifies the language I think using the Local ID as LangID will be better or it can be added as a new column in the table. Then we have the language name stored the name of the language written in that language so this column must have NVarChar type. Also we have Language direction identify if the language displayed in right-to-Left or left-to-write order. This information can be retrieved from the CultureInfo object so we can neglect it from the table.

Sometimes the system users table has a column that refers to the default language for the user. Some times its gained from the current culture of the operating system deployed in the user machine. I think prefer storing it in the users table.

Let us move now for the most important part of the system. How to design the database to support multilingual content? First design your database without considering its multilingual. Then, for each table has columns may contain information varying from language to another: first: leave the columns that not depending on the language in the same table then add a new table have a composed primary key (the key from the parent table and the language) and move all the columns depending on the language into that table. So in the new table the parent table primary key will be a foreign key to the parent table.

So, if we have a branches table contains: branch id, name, address, manager and telephone number. We can put the branch ID, manager and telephone in the parent table. While the child table will contains branch ID, language, name and address. Branch ID is a primary key for the parent table. In the child table, the primary key is composed from branch ID and language. Branch ID is a foreign key in the child table.

So if we have the branch data as following:


English Name

Arabic Name

Manager ID


English Address

Arabic Address


Cairo Branch

فرع القاهرة





Then we need to add a record the branch table:


Manager ID





And two records in the branch details table:



Branch Name

Branch Address



فرع القاهرة




Cairo Branch


In the next post I will continue the talk about the data layer

Multilingual System Design: (1)Overview

May 13, 2008

A lot of multinational companies and organizations in general have audiences around the world with different languages and cultures. These organizations have an increasing need to develop their information systems targeting these audiences with their own languages. Not only the interface but also the content of the system must match the audience language.

In this series I am suggesting a design for a multilingual system. This system has a multilingual content viewed in multilingual user interface. I used this design in many systems and was very useful. Especially when in case of medium to large systems. The systems done with this design are used in RTL and LTR orientation. But this model is design for windows application. I think it needs many modifications to fit to web based applications.

This design is designed in comply with Microsoft technologies. I tried to make it generic but when it gets specific it will tends to be Microsoftian. Because I made this design to be implemented with MS SQL and .NET technologies.

Let us start with a general overview on the system. The system is consisting of four layers:

  • Database Layer.
  • Data Access Layer
  • Logic Layer.
  • User Interface Layer.

The database layer deals with the multilingual content. Not only data structures but also the basic logic that manipulating the data. Data access layer is the layer used to retrieve data from database. Logic layer is the least layer that multilingual design affects but we will see that there are some modifications need to be done in this layer to be complied with the multilingual functionality. Finally the user interface layer is used to display the multilingual content but in a multilingual interface so the forms, messages…etc that used to view and take commands from user is also multilingual.

In the next post I will start with Data Layer ISA…