Biography of Shahrukh Khan

Biography for
Shahrukh Khan

Date of Birth

2 November 1965, New Delhi, India

Nickname

King Khan
SRK
The Unofficial Badshah of Bollywood
The Tom Cruise of India
Shahrukh
The King Of Romance

Height

5' 8" (1.73 m)

Mini Biography

Shahrukh Khan was born on 2nd November 1965. He was brought up in Delhi. He has a sister named Shehnaaz, Wife Gauri Khan, And a dog Named Chewbacca. Shah Rukh Khan has won several awards for his outstanding performance in Darr (1993), Dilwale Dulhania Le Jayenge (1995), Dil To Pagal Hai (1997), and Kuch Kuch Hota Hai (1998). Right now he is the top most actor in the India. His recent hit Baadshah (1999) has also earned many praises. His latest hits are Chak De! India (2007), and Om Shanti Om (2007).

IMDb Mini Biography By: rajju, rajju@email.com

Mini Biography

Shahrukh started his career on a TV serial called "Fauji" (1988), that won him instant recognition. He also acted in another TV soap called"Circus" (1989). He was born and raised in Delhi, and he was equally brilliant in studies and sports. Fell in love with a girl called Gauri Chibba who was then studying in Loreto Delhi. He later married her before he got his break in Bollywood. Currently, he is the most sought after actor in India. Has a son called Aryan Khan and a daughter named Suhana Khan.

IMDb Mini Biography By: Phoebe

Mini Biography

There is not a dot in Bollywood that does not carry Shahrukh Khan's name. He was born on 2 November 1965 in New Delhi, India. He married Gauri Khan on 25 October 1991. They have two children, son Aryan Khan (b. 1997) and daughter Suhana (b. 2000). Khan started out his career appearing in several television serials in the late 1980s. He made his film debut with the commercially successful Deewana (1992). Since then, he has been part of numerous commercial successes, as well as having delivered a variety of critically acclaimed performances. During his years in the Indian film industry, he has won seven Film Fare Best actor awards and has had significant box office success. Some of his films includes: Darr (1993), Baazigar (1993), Anjaam (1994), Kuch Kuch Hota Hai (1998), Om Shanti om (2007), Chak De India (2007) among others.

IMDb Mini Biography By: gavin (gunmasterM@hotmail.com)

Spouse

Gauri Khan

(25 October 1991 - present) 2 children

Trade Mark

His Dimples

His Smile

Trivia

Studied in St. Columba's school, New Delhi, where he was awarded the 'Sword of Honor', essentially the award for best student.

Although his birth name is spelled Shahrukh, he prefers and signs his name as Shah Rukh.

Hindi megastar

Number one Indian star actor in the 1990s, but is now (2000) seriously challenged by the new wonder boy Hrithik Roshan who has become the number one phenomenon in India at the start of the new millenium.

Father of Aryan Khan and Suhana Khan.

2 children with Gauri, Aryan and Suhana

He agreed to star in Aditya Chopra's films without looking at the script first.

One of the four Khans that ruled Bollywood in the 1990s till now (2000's). The other three are Salman Khan, Saif Ali Khan and Aamir Khan.

Formed a popular screen couple with Kajol and Juhi Chawla.

Runs a production company "Dreamz Unlimited" with actress, friend, co-star Juhi Chawla and director, friend Aziz Mirza.

Married to Gauri Khan

Named one of Time Magazine's 20 Asian Heroes under 40 (2004)

His son, Aryan Khan, portrayed SRK as an infant in Kabhi Khushi Kabhie Gham... (2001).

Son, Aryan Khan, voice of Tez Lajawaab (Dash), character for Hindi dubbed version of Disney's animated film, The Incredibles (Hum Hain Lajawaab).

Shah Rukh and his wife, Gauri Khan, own the production company "Red Chilies Entertainments", which Shah Rukh started for friend and colleague, director/choreographer Farah Khan, for her debut directorial film - Main Hoon Na (2004).

Purchased a villa on a man made island on the coast of Dubai in the United Arab Emirates.

#74 on E!'s 101 Hottest Celebrity Bodies Countdown (aired January 2006)

Was not very good at Hindi in school, until his mother promised to take him to the cinema if he passed. As he loved films,he got top marks from then on.

His father ran a transport company and his mother was a magistrate.

Gets along very well with former co-stars Juhi Chawla and Preity Zinta.

Loves computer games, video games and hi-tech gadgets.

His first name "Shahrukh" means "face of the king".

Resides in a mansion called Mannat in Mumbai, India.

Being a Muslim man married to a Hindu woman, he and his wife combine both religious backgrounds into their children's education.

His parents died before he entered movies. Shahrukh considers it a big regret that they couldn't see what their son was to become.

Has a mannequin of himself in Madam Tussaud's Museum in England. Along with Amitabh Bachchan , Salman Khan and Aishwarya Rai Bachchan.

He has a dog called Chewbacca.

He has an elder sister named Shehnaz Lalarukh.

Father is Meer Mohammad Taj Khan, mother is Lateef Fatima Khan.

Fond of BMW cars and owns a number of them including the latest models.

His favorite drink is Pepsi Cola.

Best friends with Sanjay Dutt, Aamir Khan, Vivek Vaswani, Saif Ali Khan, Arbaaz Khan, Hrithik Roshan and his wife Sussane Khan Roshan,Vivek Oberoi, Juhi Chawla and her husband Jai Metha, Rani Mukherjee, Karan Johar, Sajid Khan, Jackie Shroff, Anil Kapoor, Farah Khan, Kajol,Malaika Arora , Chunky Pandey and his wife and Mushtaq Sheikh.

Younger brother of Shehnaz Lalarukh.

His favorite food is Tandoori Chicken and Chicken Thikka.

Suffers from back, knee and neck problems.

Firmly insists and had promised himself that he would never kiss on the lips of any of his female co-stars after he had done the movie Maya Memsaab.

Launched Deepika Padukone's career in Bollywood.

His Father Meer Mohammed Taj Khan died of Cancer in 1981 and his Mother Lateef Fatima Khan died of complications in Diabetes in 1991.

He has been awarded the Ordre des Arts et des Lettres (Order of the Arts and Literature) award by the French government for his Exceptional Career.

Launched his perfume "SK" with the French perfumers and Jeannes Arthes.

The reason why Khan took up Mass Communications (film making) is because he loved Television commercials.

Had Graduated from Hansraj College, Delhi University and followed it up with a Masters Degree in Mass Communications (Film making) from Jamiya Milia Islamiya University, in New Delhi, but after a year Shah Rukh opted out as he had to make his acting career in Bollywood.

He had captained all teams in football, cricket and hockey and even played cricket at Zone and National level.

At school he was an ace in Hindi, Electronics and Biology but wasn't good at all in Mathematics.

His debut film was Dil Aashna Hai but due to the delay in the release of the film Deewana was considered as his debut film.

His acting career in Bollywood was launched by his friend Vivek Vaswani and Hema Malini.

Is very scared of riding horses.

Was not at all interested to act in Bollywood films but then he had decided to act in films to secure his families future and earn a lot of money.

Knew Manoj Bajpai as they both studied acting in the same theatre group with Barry John.

For a short span of time Shahrukh ran a restaurant in Dariya Ganj in New Delhi, India.

SRK joined Barry John's theatre group in New Delhi and learned acting from him, Barry John also taught acting to Manoj Bajpai in his theatre group.

Owns three Production Houses in India, Dreamz Unlimited, Red Chillies Entertainment and Red Chillies Idiot Box. Red Chillies Idiot Box Production house will start producing Television Serials in India.

Has started producing Television Serials in India.

Turned down the Quiz Master's (Prem Kapoor) role in Slumdog Millionaire and the role went to Anil Kapoor.

Owns a VFX company, Red Chillies VFX.

Personal Quotes

(December 2001, about Hrithik Roshan): I wish I looked as good as he does. And I wish I danced as well as he does!

Yes, I do have a close circle of friends and I am very fortunate to have them as friends. I feel very close to them I think friends are everything in life after your family. You come across lots of people all the time but you only make very few friends and you have to be true to them otherwise what's the point in life?

I'd rather sink trying to be different, than stay afloat like everyone else

I cannot repay my fans for what they have done for me, they have given me so much love and that love has taken me to the number 1 position where I am today, the only thing I can do for my fans is to never stop working, and to do films till the very end, it is the only way I can express my love for them.

To me, Devdas is the end of love stories. I've portrayed an obsessed lover, a nice lover, an angry lover, a romantic lover. And now I've played Devdas. For someone who doesn't even like love stories, I've played an awful lot of lovers. Personally speaking, I wouldn't see any of the romantic films I've acted in.

I'm the luckiest man in the world and I don't want to hide from the faces I'm acting for. So I don't surround myself with guards, I've never given an interview in which I've said I feel bad that I can't go shopping or I can't go to Chowpatty and eat bhelpuri without being mobbed. I'm not the kind of guy who goes out wearing dark glasses (I don't think I'm a big enough star to hide behind them, honest). I go to see movies in the cinema theatres, I go to restaurants with my family and friends even though I know people are going to disturb me there.

God has become a generic term like `mind blowing.' It is embarrassing. I would have said that to Amitabh Bachchan, Naseeruddin Shah, Nana Patekar. I used to tell them I want to stand in the same space as you. I've told Kamal Haasan, I just want to touch you. They are the gods of acting. When people call me God, I say, no, I'm still an angel or saint of acting. I still have a long way to go.

(August 2004): Awards that ignore me are losers.

(August 2004): I'm try-sexual. I try anything that's sexual.

(August 2004): I have no competition. Every year the names I'm pitted against keep changing. You can't cream the competition, you have to kill it.

I keep hearing that our films are escapist and unreal but I find our films the most real in the world. We don't have people going up in a rocket and single-handedly blowing up a meteor. We don't have a president on Air Force One saving the world or things coming out of people's stomachs. Our fantasies and escapism are real. It's just people singing and dancing in the street. If England had won the World Cup you would have seen people singing and dancing like that.

I don't like wearing dark glasses. I'm happy with the fact that people know me. I want people to scream and shout at me, I want people to trouble me when I'm having lunch, I like six bodyguards around me. I love being a star. I find it very strange when people who are famous say they don't want to be photographed. I don't want to be photographed first thing in the morning, I don't want people peeping into my bedroom, but besides that, it's a wonderful life.

"I haven't given up smoking. I'm very clear about it, it's a personal choice. I want to cut down on it. It shouldn't be made into an issue to say, damn good or damn bad. Whether I give it up or not shouldn't be an issue." (Movie Mag, May 2006)

"I was supposed to have done Rang De Basanti (2006), the guy on the motorbike. I didn't have the dates. They were shooting in Delhi and the dates were clashing with Paheli." (Movie Mag, May 2006)

"It's not like Steven Spielberg is waiting with a script for me. I don't think I'll ever be offered a great international film in my lifetime, so I'd rather be a king here. Moreover, Indian cinema is the greatest in the world. But of course, after spending three months in LA, London, and New York I found that our cinema is a little exaggerated. To make a mark in the West we have to reach their level without losing our identity, culture or songs. I don't want to star in a Hollywood film, but want to make a film that crosses over universally." (Movie Mag, May 2006)

On trying to get Paheli (2005) an Oscar nomination: "There's a misreport here about our lobbying at the Oscars. The understanding that we have of the Oscars is very different from how it really is. Because Indian film, foreign films are not known, you're supposed to hire a PR company which we did. It's not as if you just go there, show your films, lobby and talk to them. You're not allowed to lobby as in you're not allowed to meet the Academy members, talk to them or even make a call to them. You just keep advertising in the 'For Consideration For Oscars' category. We took out full page ads in papers like Variety and Hollywood Reporter. The only good thing we did was that we advertised very frequently, it was promoted on the same scale as the biggest of films. We did it because we could afford it." (Movie Mag, May 2006)

"I felt Asoka (2001) should have been chosen for the Oscars. We had worked towards that. We had these international distributors for it. We were the first to actually release an Indian film internationally in traditionally non-Indian theaters. We spent a lot of money and lost a lot of money too. We were the first to put up boardings in London, in tube stations. We did speak to everyone who was anyone here, wondering if Asoka could go to the Oscars. But the one that got chosen was Lagaan: Once Upon a Time in India (2001) which was even better. So we had no complaints. After that I didn't make any film for the foreign market." (Movie Mag, May 2006)

You must respect your seniors, bu never get intimidated by them. Winning should be a habit, not an option. The four Hs are important when you play to win --- honesty, humor, hard work and a bit of haraamipan.

I don't look at the figures that my movies make. The only figures I look at are girl's figures. (When asked to comment on what he felt about the figures his movies gross.)

Whenever I fail as a father or husband... a toy and a diamond always works.

If I talk to a girl, it's assumed that I'm having a scene with her. If I don't, then it's assumed that I'm gay.

I don't kiss on screen. Period.

There are only two Khans. Ghenghis Khan and Shahrukh Khan

Sex is not required to sell my film. My name is enough.

You never win the silver, you only lose the gold.

I am very shy. If I am flying British Airways and the air hostess asks me two questions, and I don't understand her accent - I will go hungry for the entire flight.

The dream I chased, took me on a journey. A journey more rewarding then the goals, the achievements. When I look back it's like facing a million mirrors. Each reflection opens a window. A window to the world I've just discovered. The world I want to share with all of you.

If I am a role model, I must be the worst one in the world.

I've never had a girl make a pass at me.

Togetherness, passion, laughter, faith, trust and jealousy are the essential ingredients of love.

The collar-bone is my favorite part of the human body.

If asking me whether sleeping with X or Y gives the media pleasure, then so be it. It's a small price to pay.

Microsoft .NET

Introduction

In the current Internet scenario, various classic applications run on multiple networks. These applications could have been written using different languages like Visual Basic, Visual C++. For example, a retail organization would have different systems, such as an inventory management system, a bill of material systems, and a general ledger system, all implemented using various technologies available for application development. These systems need to be integrated to form a higher-level enterprise information system for an organization. To do so, application developers had to use technologies such as Microsoft Distributed Component Object Model (DCOM), Component Object Model and so on. However, these distributed technologies are very tightly coupled to the programming languages in which these applications have been developed. This leads to problems in application integration if the applications have been developed using disparate technologies.

Developers who have developed applications using Microsoft technologies have extensively used Component Object Model (COM) technology to develop components. These components were used mainly to encapsulate the business logic of the application. COM technology suffered from the following limitations:

• Registration of COM components.
• Unloading COM components.
• Data link library (DLL) hell.

Microsoft .NET has been developed keeping the above limitations in mind and making Web services development one of its major goals.

Automatic Memory Management.

• To provide a very high degree of language interoperability
• To provide a runtime environment that completely manages code execution
• To provide a very simple software deployment and versioning model
• To provide high-level code security through code access security and strong type checking
• To provide a consistent object-oriented programming model
  To facilitate application communication by using industry standards such as SOAP and XML.
• To simplify Web application development

Proposed Solution:

Interoperability

The interoperability features of .NET allow you to work with existing unmanaged code (that is, code running outside the CLR) in COM components as well as Microsoft Win32 DLLs. It also allows you to use managed components from your unmanaged, COM-based code. These features allow you to choose if and when to migrate existing unmanaged code to .NET.

The various types of interoperability supported by .NET

Calling a COM component from .NET - When a COM object is called from .NET, the runtime generates a runtime callable wrapper (RCW). The RCW acts as a proxy for the unmanaged object.

The RCW is responsible for handling all interaction between the .NET client code and the COM component, including (but not limited to):

• Creating and binding to the underlying COM object.
• Consuming COM interfaces and factoring the interfaces into a managed form.
• Translating and marshaling data between environments.
• Managing the lifetime of the wrapped COM object.
• Translating COM HRESULT values into .NET exceptions

Calling a .NET component from COM.

When a .NET component is called from COM, the runtime again generates a wrapper object to bridge the gap between the environments. In this case, the runtime generates a COM callable wrapper (CCW). The runtime reads the type information for the component from its assembly metadata and generates a compatible CCW. Similar to the RCW, the CCW acts as a proxy between the unmanaged COM code and the managed .NET code.

Calling unmanaged application program interface (API) functions from .NET.

This interoperability, called Platform Invocation (commonly abbreviated as P/Invoke), allows managed code to call into C-language-style API functions, handles the marshaling of data types between managed and unmanaged types, finds and invokes the correct function in the DLL, and facilitates the transition from managed to unmanaged code.

A good example of P/Invoke functionality is calling one of the many Win32 API functions exposed by the Windows operating system. Through P/Invoke functionality, the runtime also supports callbacks from API functions. The current release of .NET, however, does not support calling from a Win32 DLL into .NET managed code. To call directly from unmanaged code to managed code, you must use COM interoperability.

Migration

Once you decide to migrate part or all of an existing application to .NET, you will need to decide how best to approach the migration. There are two major approaches to migration i.e. horizontal and vertical. Horizontal migration involves replacing a whole tier of your application. For example, you may choose to replace the ASP code within your Web-based presentation tier, or you may replace the COM code within your middle tier as the initial migration step. Vertical migration involves isolating and replacing a piece of your application through all n tiers.

Guidelines

• Choose a migration strategy that minimizes the risk of migration.
• Choose migration activities that allow you to continue to use your existing COM code base as you move to .NET.
• Quickly take advantage of the new features provided by the .NET environment.

Horizontal Migration - In a horizontal migration, you migrate an entire tier of your Windows DNA-based application to .NET without immediately migrating the other tiers. By migrating a single tier at a time, you can take advantage of the features of the .NET Framework specific to a particular tier (for example, ASP .NET on the presentation tier), in many cases without modifying application code or affecting operations on another application tier.

Choosing a horizontal migration strategy

The first step in a horizontal migration is to decide which tier to migrate first.

To replace the Web tier, you replace ASP code with code developed using ASP .NET. You may also externally expose much of your middle-tier functionality with .NET Web services. Ideally, the Web tier can be replaced with few or no changes to the middle tier. If you migrate your Web tier to ASP .NET you can make use of the following features:

• Advanced data binding functionality
• Easier configuration management
• Improved session state management
• Advanced caching capabilities
• Easy development of Web services
• Compiled code, which results in better performance
• The Web Forms programming model with server-side event handling
• Server-side controls, which make it easier to develop solutions targeting multiple browsers

To replace the middle tier, you migrate your middle-tier COM components to .NET with few or no changes to the Web tier.

In deciding whether a horizontal migration strategy is appropriate, and if so, which tier is the most appropriate for initial migration, consider whether your existing Windows DNA-based solution has the following characteristics:

• Large number of Web servers
• Shared code migration
• Heavy use of ASP Application or Session state
• Complex middle tier

Vertical Migration - Another migration approach is to migrate a portion of your application vertically through all application tiers. This essentially involves carving out a piece of your application that has minimal interaction with other pieces and migrating it. This includes both ASP code and COM components. An example might be converting the search functionality of your Web site to .NET, including the presentation tier, business tier, and data tier. The remaining functionality of the site is left in traditional COM and ASP until the time is right for migration to .NET, based on your project schedules, resources, and current system architecture. Any remaining interfaces between the new managed code and the unmanaged code function through COM interoperability.

Choosing a vertical migration strategy

You might choose to adopt a vertical migration strategy for a number of reasons:

• Good application isolation - If parts of your application are well isolated from other parts of your application, you have an excellent candidate for vertical migration. Parts of an application that are well isolated share very little state information with the rest of the application and can easily be migrated with little impact on the rest of the system.
• Adding new functionality to an existing application - when adding new functionality to an existing application, you should strongly consider using the .NET Framework to develop the new functionality.
• Heavy use of ADO recordsets between tiers - many applications pass disconnected ADO record sets from the data and business tiers to the presentation tier. They then iterate through the record sets and generate HTML tables. This type of application is well suited to a vertical migration.
• Planning to re-architect - If you plan to re-architect your application, vertically migrating part of your application to the new architecture provides a good test bed for the new design. The .NET Framework also makes it easier to provide the functionality that newer architectures are built on.

Vertical migration considerations

Before undertaking a vertical migration, you must consider the following issues:

• Application-slicing for a vertical migration
• Migration of shared code
• Session and application state management in a mixed ASP/ASP .NET environment
• Interaction between ASP and ASP .NET code in a mixed ASP/ASP .NET environment
• Interoperability and translation of managed and unmanaged data types
  CLR deployment
• Application deployment
• Configuration of COM+ based applications and .NET Enterprise Serviced Components
• Optionally using Application Center 2000 to ease deployment

Interoperability vs. Migration

The first thing to consider in terms of a migration is whether to migrate the code at all. The COM interoperability features of the .NET Framework are very powerful and, in nearly all cases, allow you to continue to use your existing code without migrating it to managed code. As you develop new parts of your application or reuse components of your application from newer managed code applications, in most cases you can simply call your existing components through the COM interoperability functionality provided by .NET. Interoperability allows you to preserve the investment that you have already made in developing and stabilizing the code, familiarizing developers with it

Performance

Overall, the overhead of calling from managed code to unmanaged code through COM interoperability is minimal. If your method performs any substantial tasks, it is likely that the overhead from the interoperability layer will be a negligible percentage of the overall method call time. However, if your method does nothing more than set a value for a property or perform some other small task, the overhead of the interoperability layer may be a significant portion of the method call. If your interface is made up of a number of these property sets and gets, known as a chatty interface, the interoperability cost may be unacceptably high.

Enhancing Development Productivity

The .NET development environment provides significant improvements to the COM-based development model for distributed applications and can significantly enhance developer productivity. If your application is expected to undergo a number of changes and development cycles in the future, you should consider migrating the application to take advantage of the higher developer productivity inherent in the .NET development platform.

Using a Managed Object Model

If most clients of your existing components will be written in managed code, you should consider either migrating your component to managed code. Your managed code clients will expect your component to look and act like a managed object. Although the RCW makes the component look somewhat like a managed component, it does not change the underlying interfaces to the component. When developing against your unmanaged component through COM interoperability, managed code developers will not be able to use parameterized constructors, static methods, inheritance, and other features they are accustomed to working with in managed code. Migrating your component or writing a managed wrapper will make your component easier to use for managed code developers.

Taking Advantage of .NET Features

In some cases, you will want to migrate parts of your application to .NET so that you can take advantage of the new features that the .NET Framework offers. For example, ASP .NET provides advanced data binding, browser-dependent user interface generation, and improved configuration and deployment. You should evaluate when the value of bringing these new features to your application outweigh the cost of code migration.

Implementation Details:

As an application developer you can face some issues as you develop your migration and interoperability plan.

- Choosing which pieces of your application to migrate
- Migration to and interoperating with ASP .NET

Choosing Pieces of Your Application To Migrate

Choosing the right pieces of your existing application to migrate is an essential task in ensuring a successful vertical migration. It is recommended that you perform a code path analysis on your current application.

Code path analysis

A typical Windows DNA-based application consists of one or more ASP pages with which a user interacts. Those ASP pages call one or more COM components, which in turn may call additional COM components. The COM components eventually access a database and either store data or retrieve data on behalf of the user. The ASP pages and components that are used during the user's single interaction would be considered a code path.

In many cases, the objects used in a code path neither depend on nor access other components in the application. Distinct code paths are a natural place to consider isolating a piece of your application for migration to .NET. Code path analysis of the application typically results in discovering pieces of your application with minimal interaction with other parts of the application, thereby minimizing interoperability needs. You can use code paths to help identify which pieces of an application are suited to vertical migration.

Interoperability for shared components

An analysis of your Web site in terms of the code paths is likely to identify components that are shared among multiple code paths. In a vertical migration, these components can be accessed through the COM interoperability functionality until all the code paths that interact with the component have been migrated. Code paths that share components between them are good candidates for migrating concurrently, minimizing the COM interoperability required.

ASP .NET Migration Guidelines

Migration guidelines specific to migration from ASP to ASP .NET and interoperating between the two environments.

Avoid or replace the ASP session object

You cannot share session state across a mixed ASP/ASP .NET environment using the intrinsic Session object. In a vertical migration, the best way to avoid this problem is to not use the intrinsic Session object in your ASP application. Numerous methods exist for working around server-based session storage and allowing information to be passed from page to page. All these methods work with both ASP and ASP .NET:

• Using cookies
• Using hidden form fields
• Encoding session information in URL strings (URL munging)
• Manually storing and retrieving session information from the database through direct ADO (from ASP) and ADO .NET(from ASP .NET) calls
• Using a custom session object that stores state in a database (This method is discussed in the following section.)

If your application does not already make heavy use of the Session object, you should generally use one of the first three methods in the previous list, all of which avoid sharing session state on the server.

Sharing state using a database

The ASP .NET Session object has the ability to store session data in a Microsoft SQL Server database automatically. However, you cannot access this data from ASP (it is stored in a binary format, which is not easily read) without considerable work and custom code on the ASP side. You also cannot directly instantiate the ASP .NET Session object through COM interoperability and use it to retrieve the session state. So, abstracting the storage and retrieval of session information away from the ASP/ASP .NET layer involves replacing the use of the built-in session object with a custom implementation for storing session state.

Any replacement used for the Session object should follow the dictionary pattern adopted by the intrinsic session objects, and should be capable of storing and retrieving named value pairs, for example:

mysessionobject("somekey") = "somevalue"

By adopting this pattern, you can replace the intrinsic session object in your existing ASP code quickly and easily. When the remaining parts of your application are converted to .NET, you can easily replace the custom implementation with the native ASP .NET session object.

Remember that if you use a custom session object (written as a COM object), each call to the object from ASP .NET will go through the COM interoperability layer, so you should try to minimize the amount of interaction you have with the session state object. Another option is to simply have separate code in each environment that reads and writes session information to the same external database.

Avoid or replace the application object

In a vertical migration, application state (in addition to session state) cannot be directly shared between the two environments using the intrinsic Application objects. Typically, the majority of information stored in application state is either data or objects that are expensive to create for each page, and is created and initialized in the Application_OnStart event in the application's global.asa file.

The simplest method for dealing with this issue is to recreate the data and objects in both environments. This allows you to maintain your existing ASP application environment and also take advantage of the equivalent and enhanced ASP .NET features such as improved caching, tracing, and deployment. This approach works well if the data is fairly static; however, if you change the data frequently, you will need to do additional work to keep the data synchronized between the environments. If you do not want to store the data in both ASP and ASP .NET, or if you change the data frequently, you will need to find an external place to store it that is accessible from both environments such as a SQL Server database.

Use Response.Redirect

You cannot use Server.Transfer and Server.Execute between ASP and ASP .NET pages. For interactions between the two environments, use Response.Redirect instead.

Security

ASP .NET does not enable impersonation by default. If you use impersonation within the presentation tier to enable role-based security in the middle tier, you must explicitly enable impersonation in ASP .NET. The impersonate attribute of the identity tag in your web.config file should be set to true. For example: