Friday, June 4, 2010

Facebook at business

I had a long training about how to make the applications like Facebook

visit https://www.salesforce.com/au/chatter/

in reference to: Facebook (view on Google Sidewiki)

Tuesday, April 24, 2007

Enhanced Document workflow approval v2

The purpose of the article

Demonstrating these extra features

• Moving all interfaces in 1 assembly and all other projects will reference this assembly.

• Registering the services "out of the box and custom services" in application configuration file for better maintenance.

• Using "out of the box" system diagnostics LogToFile utility .

• Using "out of the box" WorkflowCommitBatchService, internally with using TransactionScopeActivity

and preparing our document service to work with batches and transactions.

• Using Fault Handler Activities to handle workflow internal errors.

• Bi-Directional communication, workflow with the host, through the custom service.

• Using "out of the box" SqlTrackingService, for tracking the workflow

• Using SqlTrackingService utility for query the tracked workflow.

If you did not read, the first article Document approval workflow system

I encourage you to read the article, and to run it, because this article is enhanced version for better design,

and for more workflow services.

Enjoy the full article

http://www.codeproject.com/useritems/wwf_basic_v2_files.asp

Windws, workflow foundation, Document approval workflow system V1

The purpose of the article

Demonstrate, a quick view of workflow foundation, and highlight the basic knowledge that

we should know before create first useful workflow application,

and highlight a design guide lines to create reusable workflow applications.

Finally, to taste the workflow through a sample project that is generic and useful for any

document workflow system, from the client application to administration application using

database.

Enjoy the full article

http://www.codeproject.com/useritems/wwf_basics_files.asp

Provider Pattern

Introduction

Provider pattern, is one of the most interested features, that introduced with Microsoft in

.Net2,

A lot of features including membership providers, roles providers, profile providers,

Health monitor event providers, Site Map providers, and more had the same design

concept.

These features not changeable but extendable, and that is beauty of provider pattern,

in this article I will demonstrate the concept of provider pattern itself,

and how easy to create your own services designed by provider pattern,

and make your services extendable and reusable.

Enjoy the full article

http://www.codeproject.com/useritems/provider_pattern_files.asp

Testable Applications

Introduction:

Many of us hear today about unit test, and mock objects, other may touched unit test first

time with NUnit tool

http://www.nunit.org/

Or through visual studio 2005 Team Suite, There are many articles about how to create unit

test, or how to test your applications And how to use different patterns for test.


This is not the target of this article, this article focus in how to create testable application

Or how to refactor your normal application code, to be testable code.

Enjoy the full article
http://www.codeproject.com/useritems/testable_applications.asp

.NET like Access(V1)

Introduction

Every programmer has a big dream "Programming without code". Practically a lot of database tools offer programming without code, the best two tools that I tried are Microsoft Access and PowerBuilder.

If you developed applications using Microsoft Access, you will realize that developing with Access is not as easy as you thought it would be at first sight. After you use the wizard and are happy with the generated application, you will realize that you do not have a menu or MDI forms. In addition, you cannot do many trivial things unless you change the normal flow of Access, for instance if you want to create a dropdown combo box and fill it with a certain value in filter form, you cannot do so and it is obvious that you cannot make a true .exe Application.

Rapid Application seems very powerful as long as it is driven in the normal way, and is hard to customize.

Power builder was another tool. It is much more powerful than Microsoft Access INMHO but, if you use a readymade library you have to understand it completely, because any customization means you need to override a function with a new one.

So the conclusion is, if you use a powerful programming tool (like ASP.NET, .NET Windows Forms, Delphi, C++ Builder (that is what I used)) with a powerful programming library to inherit and use, and you know how to enhance and override functions, it is the best solution.

Now here you are, that is .NET as a Rapid database tool.

I implemented this idea earlier in PowerBuilder with three levels of inheritance. It took three months to develop and once I finished it, it spread out very quickly and many companies used it.

So I can easily apply the same concept in .NET Application.

Just create the library and you will inherit and use it, and it automatically works fine and is more powerful and easy than Microsoft Access.

enjoy the full article in code project

http://www.codeproject.com/cs/database/DBLibrary.asp