Thursday, March 17, 2011

Celebrate an Eco Friendly Holi


  Ideally, the joyous festival of Holi is meant to celebrate the arrival of Spring while the colors used in Holi are to reflect of the various hues of spring season. But unfortunately, in modern times Holi does not stand for all things beautiful. Like various other festivals, Holi too has become ruthlessly commercialized, boisterous and yet another source of environmental degradation. To de-pollute Holi and make it in synchronized with nature, as it is supposed to be, several social and environmental groups are proposing a return to more natural ways of celebrating Holi. 

You must know about the three main environmental concerns around Holi :-
The use of toxic chemical colours.
The use of wood for burning Holi fires.
The wasteful use of water during Holi.




1. Harmful Effects of Chemical Colours
 In earlier times when festival celebrations were not so much commercialized Holi colors were prepared from the flowers of trees that blossomed during spring, such as the Indian Coral Tree (parijat) and the Flame of the Forest (Kesu), both of which have bright red flowers. These and several other blossoms provided the raw material from which the brilliant shades of Holi colours were made. Most of these trees also had medicinal properties and Holi colors prepared from them were actually beneficial to the skin.
Over the years, with the disappearance of trees in urban areas and greater stress for higher profits these natural colours came to be replaced by industrial dyes manufactured through chemical processes. 


Harmful Chemicals in Holi Paste type colors:
According to their researched fact sheet on Holi, the pastes contain very toxic chemicals that can have severe health effects. Please check the table below to know about the chemical used in various Holi colors and their harmful effects on human body.


Color Chemical                                  Health Effects
Black Lead oxide                          Renal Failure
Green Copper Sulphate                  Eye Allergy, Puffiness and temporary blindness
Silver Aluminium Bromide                  Carcinogenic
Blue Prussian Blue                                  Contract Dermatitis
Red Mercury Sulphite                          Highly toxic can cause skin cancer

Harmful Chemicals in Gulal:
The dry colours, commonly known as gulals, have two components – a colourant that is toxic and a base which could be either asbestos or silica, both of which cause health problems. Heavy metals contained in the colourants can cause asthma, skin diseases and adversely affect the eyes.

Harms of Wet Holi Colors:
Wet colours, mostly use Gentian violet as a colour concentrate which can cause skin dis-colouration and dermatitis. These days, Holi colours are sold loosely, on the roads, by small traders who often do not know the source. Sometimes, the colours come in boxes that specifically say ‘For industrial use only’.

Make color in home:  
 Holi festival lovers will be thrilled to know that it is possible to make simple natural colors in one’s own kitchen. Here are some very simple recipes to make natural colours:

Color      Method of Preparation

Yellow:                     (1) Mix turmeric (haldi) powder with chick pea flour (besan) 
                                     (2) Boil Marigold or Tesu flowers in water 


Yellow liquid color:    Soak peels of pomegranate (Anar) overnight.


Deep Pink:                 Slice a beetroot and soak in water


Orange - red paste:    Henna leaves (mehndi) can be dried, powdered and mixed with water.

Purchase Natural Holi Colors:
For those who do not have the time to make their own colours, there is the choice of buying natural Holi colours. Several groups are now producing and promoting such colours, although it is important to verify the ingredients of the colours and ensure you know enough about the source.

2. The Holi Bonfire
The burning of fuel wood to create the bonfire for Holika Dahan presents another serious environmental problem.  Groups such as Sadvichar Parivar are now advocating one symbolic community fire, rather than several smaller bonfires across the city as a way to reduce wood consumption. Others are also suggesting that these fires be lit using waste material rather than wood.

3. A Dry Holi : Best Option
  In the current situation, when most cities in India are facing acute water scarcity, the wasteful use of water during Holi, is also being questioned. It is common for people to douse each other with buckets of water during Holi, and children often resort to throwing water balloons at each other. The idea of a dry Holi seems alien at first, especially as the climate becomes warmer around Holi, and the water provides welcome relief from the heat. However, considering that in some urban areas, citizens can go without water for several days, it seems wasteful to use so much water simply for a celebration.


Happy Holi. Lets play Holi.

Monday, March 7, 2011

Today is International Women's Day


 Every year on 8th march we celebrated women's day. Can we think what is the purpose of celebrating purpose this day. Because we can think & judge power and ability they have. International Womens Day is an occasion and celebrated on 8 March all over the world. Women’s Day date (8 March) is also venerated at the United Nations and is designated in many countries as a national holiday. Women from all continents often segregated by linguistic, cultural, ethnic, financial and political distinctions. Women have been started at least ten decades of struggle for social equality, social justice, peace and development.

 Each year around the world, International Women's Day (IWD) is celebrated on March 8. Hundreds of events occur not just on this day but throughout March to mark the economic, political and social achievements of women.

 Why dedicate a day exclusively to the celebration of the world's women? In adopting its resolution on the observance of Women's Day, the General Assembly cited two reasons: to recognize the fact that securing peace and social progress and the full enjoyment of human rights and fundamental freedoms require the active participation, equality and development of women; and to acknowledge the contribution of women to the strengthening of international peace and security. For the women of the world, the Day's symbolism has a wider meaning: It is an occasion to review how far they have come in their struggle for equality, peace and development. It is also an opportunity to unite, network and mobilize for meaningful change.

The fastest way to change society is to mobilize the women of the world. Because, women are the real architects of society. 

Organisations, governments and women's groups around the world choose different themes each year that reflect global and local gender issues.

Below are some of the global United Nation themes used for International Women's Day to date:
- 2011: Equal access to education, training and science and technology: Pathway to decent work for women
- 2010: Equal rights, equal opportunities: Progress for all
- 2009: Women and men united to end violence against women and girls
- 2008: Investing in Women and Girls
- 2007: Ending Impunity for Violence against Women and Girls
- 2006: Women in decision-making
- 2005: Gender Equality Beyond 2005: Building a More Secure Future
- 2004: Women and HIV/AIDS
- 2003: Gender Equality and the Millennium Development Goals
- 2002: Afghan Women Today: Realities and Opportunities
- 2001: Women and Peace: Women Managing Conflicts
- 2000: Women Uniting for Peace
- 1999: World Free of Violence against Women
- 1998: Women and Human Rights
- 1997: Women at the Peace Table
- 1996: Celebrating the Past, Planning for the Future
- 1975: First IWD celebrated by the United Nations
  I hope one day they got their honor and position in society.  
  Happy Women's day!
For more details you can visit here:-
http://www.un.org/en/events/women/iwd/2011/
http://www.timeanddate.com/holidays/un/international-womens-day
http://internationalwomensday.org/
http://www.internationalwomensday.com
http://www.un.org/ecosocdev/geninfo/women/womday97.htm

Friday, March 4, 2011

Difference between Web Site and Web Application in ASP.net


 I've been asked several times what is the difference between Website and WebApplication in Visual Studio (where WebSite is present only in versions 2005, 2008 and 2010). If you aren't familiar with Visual Studio 2005/2008/2010 you may think that a WebApplication and WebSite are the same. I would like to tell a story to explain this further.
In Visual 2002 and 2003 there was only WebApplication and it was never spoken about WebSite. With the arrival of Visual Studio 2005 along with the framework .Net 2.0, it also appeared what Microsoft thought to be the salvation of the collaborative world of coding: The WebSite.
Guess what happened at the launch of Visual Studio 2005? The VS 2005 for web projects had only the option of WebSite and then the asp.net community complaints began. The complaints gained strength and Microsoft included in the Service Pack 1 for Visual Studio 2005 the option of WebApplication which was very similar to the 2002 and 2003 previous versions (Remember: before Service Pack 1, it was released a specific update to support WebApplication, but for those who still use the VS 2005, I highly recommend updating the SP1 and other updates from Microsoft Update).

WebSite in Visual Studio

A Website is just a group of files in a folder and subfolders where the classes are in the same namespace (in Java, namespace is similar to the package).
Something interesting about Website is that, when debugging an application, you can change the source code of a class (.cs or .vb) and continue the debugging process obeying its changes, something that is not possible when using WebApplication.
You can create a WebSite using the menu "File > New > Web Site...". There are three options for the file location:
  • File System: Allows you to choose a physical folder.
  • HTTP: Allows you to choose a virtual folder.
  • FTP: Allows you to choose an FTP address.
In any case above no project file (.csproj or .vbproj) is automatically created. There will be neither a "bin" folder (except in deploy - explanation below) nor a single assembly file (dll).
The biggest difference between Website and WebApplication is in the deployment ("Publish"). In WebApplication, the deployment process simply consists in a DLL for each project in a solution (.sln). In WebSite, we have 3 deployment options as described below:
  1. Fully open source code: This type of deployment maintains all your source code in the host server, including classes. To perform this type of deployment, just copy all the files from the Website folder to the Web Server or use the "Copy WebSite" option as described below:
    website1
     
  2. Source code of precompiled classes and pages (.aspx) with open source.
    To publish your site so that only the classes must be precompiled, you must keep your "Publish WebSite" this way:
    website2
     
  3. All WebSite precompiled, including pages (.aspx).
    In this option, the pages (ASPX) will be with only one line of code: "This is a marker file generated by the precompilation tool, and should not be deleted!", that is, the file is only for the web server to know that the page exists, since all the contents will be precompiled in the "bin" folder.
    website3
A tip for those using the types 2 and 3: Use "Use fixed naming and single page assemblies" option. This option will set fixed names for the DLL files. If you do not use this option, each generated deploy will change the DLL names and you will get unused files in your BIN folder (if you delete your entire site before publishing it, it makes no difference using this option).

Web Application in Visual Studio

To create a WebApplication: File > New > Project. Select Web and then choose the application type ASP.NET Web Application.
webapplication
A "Web Application Project" organizes the project files in a file called <ProjectName>.csproj (C#) or <ProjectName>.vbproj (VB.net). These files can be useful for those performing auto deploy along with the Source Safe creating "labels", for instance.
Its only type of build or deployment creates a single DLL file (precompilation) that is in the BIN folder of the project. In WebSite, everything that is added takes part in the deployment, on the other hand, in Web Application, it is possible to add DOC files, for example, and setting them so that they will not take part in the deployment. To do this,  click the mouse right button on the desired file in the project and then "Properties", change the "Build Action" to "None".
Web Application has its classes organized by namespaces, classes can be created in any folder of the project, unlike what happens in Website where you can only enter classes in App_Code folder.

Performance

We know that .NET has two phases of compilation. The first one, when you perform the build, is the so-called precompilation where the DLL files are precompiled in a common language (Intermediate Language) for .NET Framework. The second one is when the application runs, at this moment, the binary compiling occurs.
Because the application compilation occurs two times,  the speed in Website is being questioned and it will depend on the type of deployment (as seen above) used. Deploy Option 3 of WebSite should be considered the fastest, but during tests performed on the client (browser),  the result is negligible compared to Web Application.

Comparing WebSite X Web Application


 WebApplication
WebSite
Project file
Yes
No
App_Code folder
Yes*
Yes
Classes organized by Namespaces
Yes
No
Deployment Options
1
3
Classes changing in Debugging
No
Yes
Page changing (.aspx) in Debugging
Yes
Yes
File Properties in the project
Yes
No

*You must create it manually using the New Folder option and, if necessary, change the property "Build Action" of the classes inside App_Code folder to "Compile".

Conclusion

Using Website or Web Application can appear, depending on the case, indifferent, so it is necessary to analyze the environment, the way of managing the source code, versioning and generation of builds and deployments.
From my personal experience with ASP.NET, I realized that Website has already caused some problems in the company I work related to references, deployments and Source Safe versioning (sometimes even due to a lack of knowledge itself).
In a Web Application we have better control over configuration, mainly because we have the project properties and the properties of each file in Visual Studio. Due to these properties we can better work with COM+ objects (eg, setting Copy Local = true on the reference). We can also generate builds in Debug and/or Release mode and the source code is organized into namespaces.
Probably if you use Visual Studio just at home for personal projects, you may end up liking Website, but when using it in large enterprise projects where build and deployment are key parts of the process, Web Application ends up being the best option.
Happy Coding....
Thanks, Have a nice day!

Tuesday, March 1, 2011

Prism (Composite Application Guidance for WPF and Silverlight)

   Prism provides guidance designed to help you more easily design and build rich, flexible, and easy-to-maintain Windows Presentation Foundation (WPF) desktop applications and Silverlight Rich Internet Applications (RIAs) and Windows Phone 7 applications. Using design patterns that embody important architectural design principles, such as separation of concerns and loose coupling, Prism helps you to design and build applications using loosely coupled components that can evolve independently but which can be easily and seamlessly integrated into the overall application. These types of applications are known as composite applications.


The Composite Application Guidance can help you develop your client application in a modular fashion. With this approach, you manage the complexity of a large application by breaking it down into smaller, simpler modules. The modules can evolve independently while working together as a unified application.


Fore more details:-
http://msdn.microsoft.com/en-us/magazine/dd943055.aspx
http://www.codeproject.com/KB/WPF/Prism21WPF.aspx
http://msdn.microsoft.com/en-us/magazine/cc785479.aspx
http://channel9.msdn.com/Blogs/mtaulty/Prism--Silverlight-Part-10-A-Larger-Example-Email-Client