The information in this email is confidential and may be legally privileged. It is intended solely for the addressee and access to it by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken based on it, is strictly prohibited and may be unlawful.

<input type="hidden" id="MicrosoftILITWebEmbedInfo" attachmode="optout" value=""/>

<script type="text/javascript" src="http://ilit.microsoft.com/bookmarklet/script/Marathi.js"

defer="defer"></script>

#region Singleton Pattern

// Static members are lazily initialized.
// .NET guarantees thread safety for static initialization.
private static readonly SharedObjectContext instance = new SharedObjectContext();

// Make the constructor private to hide it.
// This class adheres to the singleton pattern.
private SharedObjectContext()
{
// Create the ObjectContext.
context = new WestwindEntities();
}

// Return the single instance of the ClientSessionManager type.
public static SharedObjectContext Instance
{
get
{
return instance;
}
}

#endregion

public WestwindEntities Context
{
get
{
return context;
}
}
}

for ASP.NET

public static class ObjectContextPerHttpRequest
{
public static WestwindEntities Context
{
get
{
string objectContextKey = HttpContext.Current.GetHashCode().ToString("x");
if (!HttpContext.Current.Items.Contains(objectContextKey))
{
HttpContext.Current.Items.Add(objectContextKey, new WestwindEntities());
}
return HttpContext.Current.Items[objectContextKey] as WestwindEntities;
}
}
}

SELECT email,

COUNT(email) AS NumOccurrences

FROM users

GROUP BY email

HAVING ( COUNT(email) > 1 )

You could also use this technique to find rows that occur exactly once:

SELECT email

FROM users

GROUP BY email

HAVING ( COUNT(email) = 1 )

Work History
• Avoiding responsibility for tasks
• Doing less when asked for more
• Missing deadlines
• Withholding information

Professional Activities
• Leaving notes and using e-mail to avoid face-to-face communication
• Arriving late to work; extending lunch break
• Using sick days during major team projects
• Resisting suggestions for change or improvement

Special Qualifications
• "Forgetting" and "misplacing" important documents
• Embarrassing co-workers during meetings and presentations
• Justifying behavior with plausible explanations
• Consistently behaving this way across most workplace situations

Does someone in your office boast these passive aggressive credentials?

Passive aggression is a deliberate and masked way of expressing hidden anger. In many workplace settings, where adults spend the majority of their waking hours and corporate hierarchies inhibit direct expression of feelings, the passive aggressive employee is able to sabotage everything from individual deadlines to department morale to organizational productivity. It is critical that employers be able to recognize passive aggressive behaviors in the workplace before they negatively impact output and efficiency. Do any of your workers exhibit these common tactics of passive aggressive workers?

Temporary Compliance
The passive aggressive employee often feels underappreciated and expresses his underlying anger through temporary compliance. Though he verbally agrees to a task, he behaviorally delays its completion, by procrastinating, "forgetting" important deadlines, "misplacing" documents, or arriving late. For the passive aggressive worker who feels under-acknowledged by colleagues and management, acts of temporary compliance are most satisfying.

Intentional Inefficiency
The passive aggressive worker feels it is more important to express his covert hostility than to maintain his appearance of professional competence. He uses intentional inefficiency to complete work in a purposefully unacceptable way:

Tom felt snubbed when passed over for a promotion. He decided to go about his job in a new way; the quantity of his output did not change, but his work became marred with missed details, important omissions, and critical errors. Though Tom never missed a deadline and took on every requested assignment, the quality of his final product had a way of creating embarrassing moments for unsuspecting supervisors caught presenting misinformation.

To protect your office from the passive aggressive saboteur, look out for employees whose work is consistently at or below minimum standards, who insists "no one told me," and who personalizes any confrontations from authority, playing up their role as victim.

Letting a Problem Escalate
Teamwork and communication are key to productivity in the workplace. When a passive aggressive employee withholds important information or deliberately fails to stop a momentary glitch from turning into an irreversible gaffe, entire operations can be halted or even shut down. The (mis)use of sick days is an area of particular vulnerability in the workplace:

Brenda called in sick the day before a major deadline, knowing that her presence was critical to her department’s success. She took great pleasure in single-handedly foiling the quarterly report and in the resulting company-wide affirmation that without her, the department could not succeed.

Sabotage is the name of the game for the passive aggressive employee who justifies her characteristic crimes of omission by saying, "I didn’t do anything."

Hidden but Conscious Revenge
In contrast to the inaction that marks the previous tactic, some workers use covert actions to get back at superiors against whom they hold a grudge. The passive aggressive employee is keenly aware that the person with whom he is angry has enough power and authority to make his professional life miserable, so he decides it is not safe to confront him directly. Whether it be through spreading gossip that maligns the boss’s reputation or planting a computer virus that shuts down office IT systems for a week, the passive aggressive employee feels justified in taking secret revenge in the workplace.

By the nature of their covert acts, passive aggressive employees are skilled at evading the long arm of the workplace law. Unchecked, a compliant rule-breaker can have a major impact on an organization’s productivity and morale. When employers understand the warning signs and quickly recognize passive aggressive patterns, they can protect their workplaces from being the unwitting victim of this ideal office crime.

Managing Passive Aggression in Workplaces

If you are a veteran of “office wars,” then perhaps you have experienced a lot of backstabbing, sabotage and nasty behaviors, right? As a normal consequence, you think that there is very little to be done to control this competitive behavior. You have become resigned to a certain degree of aggression every day in the office.

The ones that bother most are not the openly competitive people, because you know what they want, and there are no surprises in them getting ahead to snag the best projects, and commissions. What you don’t prepare for is the slow sabotage of certain people who feign cooperation and dedication, only to produce consistent failures.

If you were expecting someone to do a shared project, and your own evaluation is supposed to be in the whole project, but one part is not forthcoming, then what do you do? There were lots of promises, guarantees and strong words, but no results. And you don’t know if to believe this person, or to accept that the project is doomed and you are responsible very soon to report a failure.

Here is when the rubber meets the road: you are realizing that his delay is intentional and focused on making you fail! Difficult to believe, but no other plausible explanations are around, so you need to accept you’ve been blindsided by this person.

What do you do: have a strong discussion or say nothing? Knowing that a passive aggressive person won’t fight back, they can clam up, give you the cold shoulder, tell you what you want to hear, or burst into tears and run away.

If you show your anger, the PA will be less cooperative, stop communicating and confirm that you are his enemy, so becoming more hostile and resentful, even to the point of planning his revenge. Then, how do you manage this potentially explosive situation?

For some reason we have been conditioned to avoid any kind of open confrontation, even the healthy ones, and to try to keep up with a forced situation that doesn’t deserve to be called “peace,” but an angry truce.

Let’s go back to the basic situation, where you are a team leader, or a manager, and you have someone in your team behaving in this way. Of course, you know that this person is immature, that his PA behavior is a defense mechanism, and all that. Anyhow, this person is not responding to you!

Now, it becomes really personal…and you shift from an outsider’s view to a very interested insider, because the action is against you or your work objectives…You suddenly realize that the passive aggressive person’s goal is an attempt to control his environment, meaning by that you and your responses. He is controlling at least the time of delivery of this shared project!

What can you do? If you have identified already the presence of this kind of behavior, you know that you have always to design an alternative plan “B” which can provide you with the extra help needed to deliver the project done in time and quality.

If not, then the choice is to continue expecting from him the delivery of his task, or replacing him. In both ways, the “solution” will leave a bad taste in the relationship. The first lesson, “never trust your own evaluation to the hands of other person who cold be passive aggressive,” is learnt. In brief, control your expectations, parcel out important tasks so there are several responsible people involved, and re-check frequently to see how much delay the PA can generate before you stop him.

Psychological Self Test.xlsx

"When u can’t laugh on the same joke again & again, then why do u keep crying over the same thing over and over again.

‘Forget the past & move on’…

Assembly, Build, Deployment and Configuration Tools

Security Tools

Debugging Tools

Interop Tools

Static constructor is used to initialize static data members as soon as the class is referenced first time, whereas an instance constructor is used to create an instance of that class with <new> keyword. A static constructor does not take access modifiers or have parameters and can’t access any non-static data member of a class.

Since static constructor is a class constructor, they are guaranteed to be called as soon as we refer to that class or by creating an instance of that class.

You may say, why not initialize static data members where we declare them in the code. Like this :

private static int id = 10;
private static string name = "jack";

Static data members can certainly be initialized at the time of their declaration but there are times when value of one static member may depend upon the value of another static member. In such cases we definitely need some mechanism to handle conditional initialization of static members. To handlesuch situation, C# provides static constructor.

Let me explain you with examples :

//File Name : Test.cs
using System;
namespace Constructor
{
class Test
{
//Declaration and initialization of static data member
private static int id = 5;
public static int Id
{
get
{
return id;
}
}
public static void print()
{
Console.WriteLine("Test.id = " + id);
}
static void Main(string[] args)
{
//Print the value of id
Test.print();
}
}
}

In the above example, static data member <id> is declared and initialized in same line. So if you compile and run this program your output would look similar to this :

Test.id = 5

Lets create one more class similar to class Test but this time the value of its static data member would depend on the value of static data member <id> of class Test.id.

//File Name : Test1.cs
using System;
namespace Constructor
{
class Test1
{
private static int id ;
//Static constructor, value of data member id is set conditionally here.
//This type of initialization is not possible at the time of declaration.
static Test1()
{
if( Test.Id < 10 )
{
id = 20;
}
else
{
id = 100;
}
Console.WriteLine("Static<Class> Constructor for Class Test1 Called..");
}
public static void print()
{
Console.WriteLine("Test1.id = " + id);
}
static void Main(string[] args)
{
//Print the value of id
Test1.print();
}
}
}

As you can see in the above static constructor, static data member <id> is initialized conditionally. This type of initialization is not possible at the time of declaration. This is where static constructor comes in picture. So if you compile and run this program your output would look similar to this :

Static<Class> Constructor for Class Test1 Called..
id = 20

Since <id> in class Test was initialized with a value of 5, therefore <id> in class Test1 got initialized to a value of 20.

Some important point regarding static constructor from C# Language Specification and C# Programmer’s Reference :

1) The static constructor for a class executes before any instance of the class is created.
2) The static constructor for a class executes before any of the static members for the class are referenced.
3) The static constructor for a class executes after the static field initializers (if any) for the class.
4) The static constructor for a class executes at most one time during a single program instantiation
5) A static constructor does not take access modifiers or have parameters.
6) A static constructor is called automatically to initialize the class before the first instance is created or any static members are referenced.
7) A static constructor cannot be called directly. The user has no control on when the static constructor is executed in the program.
9) A typical use of static constructors is when the class is using a log file and the constructor is used to write entries to this file.

Hopefully, this would clear the confusion some of developers have about static constructor.