Ujjwal's Blog: October 2013

Friday, October 25, 2013

New line break problem with EPPLUS when exporting data

Hi,

Recently i have been facing an issue while exporting data using C# and EPPLUS. I used below solution to get that done ::

Since my data is coming from stored procedure and this data is stored in a single column, i used a special character to seperate data.

ENTRY1***ENTRY2

so in excel this will be displayed as

ENTRY1
ENTRY2

if you send data from DB like for example :: ENTRY1\r\nENTRY2, it didnt work even if i convert that to a string. So, i replaced this special character in my c# code.

int rowCnt=ws.Dimension.End.Row;
for (int i = 1; i <= rowCnt; i++)
{
using (var rngs = ws.Cells["FD"+i])
{
var rt1 = rngs.RichText.Text;
if (!string.IsNullOrEmpty(rt1))
{
rngs.RichText.Clear();
rngs.Style.WrapText = true;
var rt2 = rng.RichText.Add(rt1.Replace("***", "\r\n"));
rngs.Style.WrapText = true;
}
}
}

Cheers,

Ujjwal Soni

Thursday, October 17, 2013

Internationalization in Demandware

i18n / internationalization

Although internationalization (or i18n for short) covers a number of different aspects, its primaryrole is to provide pages in multiple languages. To ensure this can be achieved, one should never include language-specific text in a template or controller directly. Instead of this, one should use the Demandware property mechanism. As familiar from languages such as Java, this permits thedefinition of entities known as "property" files, which assign the actual language-specific texts to unique keys. Since Demandware loads all property files automatically, this means you always have access to the keys of all property files.

Instead of using the Resource class from Demandware, you should utilize the i18n method provided by the framework. This offers a few extensions that, among other things, permit the utilization of property file content in frontend JavaScript functions.
Sample property file ("user.properties"):

user.profile.complete.head=Complete Your Profile
user.profile.complete.promo=What is this?
user.profile.complete.buttons.next=Next

Cheers,

Ujjwal Soni

Demandware UX Studio plugin installation in eclipse

Step 1: In Eclipse, from the main menu, select  Help > Install New Software.
The Available Software dialog appears.

Step 2: In the Work with field, enter the URL for your version of Eclipse:

    Indigo - http://updates.demandware.com/uxstudio_pr/3.7
  Juno - http://updates.demandware.com/uxstudio_pr/4.2

Step 3:  Select Demandware from the list and select Next. At this point Eclipse will compare the UX Studio requirements with what is available to ensure compatibility. After this process is complete,
the Install Details dialog appears.

Step 4:  Select the I accept the terms of the license agreements button and then select Finish. The Installing Software dialog appears showing the progress of the installation.

Step 5:  Select Yes when prompted to restart Eclipse.

Thanks,

Ujjwal Soni

Wednesday, October 16, 2013

Demandware Graphical Pipelines Disadvantages

Hi,

Below are some disadvantages i discovered while working on demandware :

The graphical pipelines have a number of disadvantages. First, they are highly static and difficult to maintain. Above all, however, it is also theoretically impossible to work on a pipeline with multiple developers. The reason for this is that even the repositioning of a single pipe let leads to changes at various places in the XML file – a file in which the pipeline is ultimately saved. This leads to a situation where conflicts that occur when merging before checking-in to a shared repository are very difficult – or impossible – to resolve. In addition, the URLs that result from the pipeline model are strictly predefined (
...demandware.../PIPELINENAME-ACTION
)

Above all, i found implementing MVC model much better and easy in comparision to Graphical Pipeline.

Comments are welcomed.

Cheers,

Ujjwal Soni

Thursday, October 10, 2013

SharePoint Vs LifeRay

Similarity between SharePoint and LifeRay

No	SharePoint Server 2010	Liferay 6.0.9 CE
1	SharePoint have web Part which only render in portion of the Pages	Liferay have Portlet which also have same feature
2	Per User Website provide by SharePoint (Standard and Enterprise Edition contain this feature)	Per User custom Page is present in Liferay
3	User Profile does collaboration part for SharePoint	OpenSocial provides collaboration plugins for LifeRay
4	Finding Employee(User) is very easily	Finding Employee(User) Search is very easily
5	Visual Studio 2010 IDE contain template for SharePoint	Ellipse or Liferay Studio IDE contain template for SharePoint
6	Multi tenancy is fulfilled with Farm / Site Collection	Multi tenancy is fulfilled with Department (as per Liferay )
7	SharePoint Setup information is store in Database and registry	Liferay Setup information is store in XML file only
8	Document Versioning and Co –Worker changes can be done in SharePoint	Liferay Plug ins Social Office provide very similar feature in it.

Difference between SharePoint and Liferay

No	SharePoint Server 2010	Liferay 6.0.9 CE
1	Publishing Feature which give provision for user to have data entry pages convert into WebPages	Liferay does not have any such provision for Publishing
2	Database is very complex and customization is not recommended	Liferay Database is very simple and custom query can be written on it
3	SharePoint Designer give huge boost to Information Worker to work on it	Information worker need to be depend Developer for lots of activity which can be done by Information Worker
4	SharePoint UI is different and learning is require	Liferay UI is very simple and easily to learn in it.
5	Lots of Activity can be done without writing single line of Code	Plugins can help but still user does not have lots of controls as compare to SharePoint
6	User can View their Microsoft Office content in the Browser	Liferay does not have this provision in it
7	SharePoint Enterprise Search is too huge and provide lots of option to filter and data gathering and so on	Liferay search is simple as compare to SharePoint Enterprise Search (Plugins can make Liferay search upto SharePoint Enterprise Search)
8	Business Connectivity Service provide option for integrated with another Enterprise Product with in Organization	Liferay does not have any such feature either Plugins or Web Service can fulfil this needs
9	SharePoint Does not have chat service integrated with it	Liferay have chat and lots of other service integrated with it (plugins are provided with setup)
10	Microsoft Own SharePoint	Community Developed and Open Source
11	Support is very Expensive from Microsoft and never come under License	Enterprise Edition provide Support which is part of the license
12	Single Instance cannot be @ zero cost ( Windows Server 2008 R2 , SQL Server 2008 & )	Single Instance can be @ zero cost (Ubantu OS, My SQL Database)

Personnel Option

Liferay is very cheap and good solution for small and mid size enterprise
Liferay UI is too good and user can learn very easily
SharePoint is good tools for Rich and Large organizations
SharePoint have lots of feature as compare to Liferay
Liferay is better than other CMS tools like Dot Net Nuke , Orchard , Word Press , Joomla or Drupal

Reference

http://www.liferay .com
LifeRay Development Guide
LifeRay Administrator Guide
http://www.microsoft.com/sharepoint