Sunday, May 17, 2009

Business Development Manager

We are Worldwide Telecom power supply manufacture is looking for professional and qualified candidates for:
Business Development Manager
Job Responsibilities:

* Develop marketing strategy to grab potential market
* Execute strategy to achieve target
* Evaluate strategy and continuously improve the strategy
* Develop the product and development strategy to meet the customer needs
* Report the target achievement to Sales Manager in HQ

Qualification:

* Wide network and relationship with Telecom operators such as Telkomsel, Indosat, XL,NTS, HCPT etc
* Bachelor degree in engineering and economic
* Experienced in marketing development strategy in telecom industry (minimum 3 years)
* English fluently is a MUST. Mandarin will be advantageous
* Good presentation, interpersonal and leadership skill
* Must have own car and driving license
* Able to work at minimum supervision and underpressure.
* Based in Jakarta
If you meet above requirements and wish to join us, please send your comprehensive resume, CV and latest photograph by using "Quick Apply" button below
( Member or Non Member)

source jobsdb

need small business, click here

...Read More

Register HTTP Handlers

After you have created a custom HTTP handler class, you must register it in the Web.config file. This enables ASP.NET to call the HTTP handler in order to service requests for resources that have the specified file name extension.

How you register an HTTP handler depends on the version of Internet Information Services (IIS) that hosts your application. For IIS 6.0, you register the handler by using the httpHandlers section of the Web.config file. For IIS 7.0 running in Classic mode, you register the handler in the httpHandlers section, and you map the handler to the Aspnet_isapi.dll file. For IIS 7.0 running in Integrated mode, you register the handler by using the handlers element in the system.WebServer section.

To register an HTTP handler for IIS 6.0

1. Compile the HTTP handler class and copy the resulting assembly to the Bin folder under the application's root folder.

-or-

Put the source code for the handler into the application's App_Code folder.

For an example of an HTTP handler.

2. In the application's Web.config file, create an httpHandlers section.

The following example shows how to register an HTTP handler that responds to requests for the SampleHandler.new resource. The handler is defined as the class SampleHandler in the assembly SampleHandlerAssembly.

type="SampleHandler, SampleHandlerAssembly" />

The following example maps all HTTP requests for files that have the file name extension ".SampleFileExtension" to the SampleHandler2 class. In this case, the handler code is in the App_Code folder, so you do not have to specify an assembly.

type="SampleHandler2 " />

Configure IIS to forward the request for the custom file name extension to ASP.NET.

To register an HTTP handler for IIS 7.0 running in Classic mode

1. Compile the HTTP handler class and copy the resulting assembly to the Bin folder under the application's root folder.

-or-

Put the source code for the handler into the application's App_Code folder.

2. In the application's Web.config file, create an httpHandlers section.

3. Create a system.webServer section inside the configuration element.

4. Create a handlers element inside the system.WebServer section.

You must define both an httpHandlers element and a handlers element.

The following example shows how to register an HTTP handler that responds to requests for the SampleHandler.new resource. The handler is defined as the class SampleHandler in the assembly SampleHandlerAssembly.

type="SampleHandler, SampleHandlerAssembly" />

Modules="IsapiModule"

scriptProcessor="FrameworkPath\aspnet_isapi.dll"

resourceType="File" />

Replace FrameworkPath with the correct path to the Aspnet_isapi.dll file.

The following example maps all HTTP requests for files that have the file name extension ".SampleFileExtension" to the SampleHandler2 class. In this case, the handler code is in the App_Code folder, so you do not have to specify an assembly.

type="SampleHandler2" />

Modules="IsapiModule"

scriptProcessor="FrameworkPath\aspnet_isapi.dll"

resourceType="File" />

Replace FrameworkPath with the correct path to the Aspnet_isapi.dll file.

For IIS 7.0 running in Classic mode, you do not have to separately use IIS Manager to map the file name extension to the Aspnet_isapi.dll file, as you do with IIS 6.0. You can map the extension in the Web.config file.

To register an HTTP handler for IIS 7.0 running in Integrated Mode

1 Compile the HTTP handler class and copy the resulting assembly to the Bin folder under the application's root folder.

-or-

Put the source code for the handler into the application's App_Code folder.

2 In the application's Web.config file, create a handlers element in the system.webServer section.

Handlers that are defined in the httpHandlers element are not used. If you do not remove the httpHandlers registrations, you must set the validation element’s validateIntegratedModeConfiguration attribute to false in order to avoid errors. The validation element is a child element of the system.webServer element.

The following example shows how to register an HTTP handler that responds to requests for the SampleHandler.new resource. The handler is defined as the class SampleHandler in the assembly SampleHandlerAssembly.

path="SampleHandler.new"

type="SampleHandler, SampleHandlerAssembly"

resourceType="Unspecified" />

The resourceType attribute performs the same function as the Verify file exists option in IIS manager for IIS 6.0.

The following example shows how to map all HTTP requests to files with the file name extension ".SampleFileExtension" to the SampleHandler2 HTTP handler class. In this case, the handler code is in the App_Code folder, so you do not have to specify an assembly.

path="*.SampleFileExtension"

type="SampleHandler2" />

resourceType="Unspecified" />

For IIS 7.0 running in Integrated mode, only the registration in the handlers element is required.

For more information about the IIS web.webServer configuration

...Read More

Windows Workflow Foundation Overview

Windows Workflow Foundation is the programming model, engine, and tools for quickly building workflow-enabled applications on Windows. It consists of a namespace, an in-process workflow engine, and designers for Visual Studio 2005. Windows Workflow Foundation is a framework which enables users to create system or human workflows in their applications written for Windows Vista, Windows XP, and the Windows Server 2003 family. Windows Workflow Foundation can be used to solve simple scenarios such as showing UI controls based on user input, or complex scenarios encountered by large enterprises, such as order processing and inventory control.
Scenarios that Windows Workflow Foundation addresses include:

• Enabling workflow within line-of-business applications
• User-interface page flows
• Document-centric workflow
• Human workflows
• Composite workflows for service-oriented applications
• Business rule-driven workflows
• Workflows for systems management
Windows Workflow Foundation provides a consistent and familiar development experience with other .NET Framework 3.0 technologies, such as Windows Communication Foundation and Windows Presentation Foundation. The Windows Workflow Foundation API provides full support for Visual Basic .NET and C#, a specialized workflow compiler, debugging within a workflow, a graphical workflow designer, and developing your workflow completely in code or in markup. Windows Workflow Foundation also provides an extensible model and designer to build custom activities that encapsulate workflow functionality for end users or for reuse across multiple projects.
The concepts in this section are inherent to Windows Workflow Foundation. They are briefly described here to provide a basic understanding. The Programming Guide section of this SDK provides implementation details and a deeper level of knowledge.
A workflow is a set of elemental units called activities that are stored as a model that describes a real-world process. Workflows provide a way of describing the order of execution and dependent relationships between pieces of short- or long-running work. This work passes through the model from start to finish, and activities might be executed by people or by system functions.
Workflow Runtime Engine
Every running workflow instance is created and maintained by an in-process runtime engine that is commonly referred to as the workflow runtime engine. There can be several workflow runtime engines within an application domain, and each instance of the runtime engine can support multiple workflow instances running concurrently.
When a workflow model is compiled, it can be executed inside any Windows process including console applications, forms-based applications, Windows Services, ASP.NET Web sites, and Web services. Because a workflow is hosted in process, a workflow can easily communicate with its host application.
The following illustration shows how workflows, activities, and the workflow runtime engine are all hosted in process with a host application.

...Read More

Exploring Sources Code © 2008 Template by Dicas Blogger.

TOPO