#dacl

Haive was aware she made a mistake right when she woke up. Non-written rule #1 of vigilantes: do not let your identity be discovered. She really hoped that was the first and last meeting she had with Mack Costas, because in return of him saving her life, she would like for Mack to keep his.

Mack Costas doesn’t know who is the woman that just materialized on his roof so badly wounded. He also doesn’t need to know who she is to be a decent person and don’t abandon her up there (like she asked). It’s not like she can refuse his help, and that’s exactly what happens when Mack carries Haive down two floors of stairs to his 12th floor apartment in the art district of San Myshuno.

After fighting Nix, Haive fled the scene before anyone could see her. She was pretty sure she killed Nix, but she had run away as fast as she could with her injuries when she heard the sirens in the near distance. San Myshuno at night was her jungle, she could find her way through with closed eyes. Mack Costas, a young photographer, also knew San Myshuno well, and that night he had found a way to access the rooftop of the apartment building he just moved in.

There is a new evil in town...people rumour she goes by Nix, but no one knows what she is really after.

What they know if that if someone can stop her, that’s Haive.

PREVIOUSLY < | > NEXT

San Myshuno never sleeps. And never stops watching. That night wasn’t going to be different, and a nosy woman that heard something on the alley called the police when she noticed two shadows that ressembled the shapes of two bodies. Haive had thought she killed Nix, she waited until she couldn’t feel a breath anymore. But she underestimated Nix’s power. It was just the beginning of the game, too early for any of them to win.

there is a new villain in town...people rumour she goes by Nix but no one really knows what she is after

   Microsoft Sunsets .NET for Oracle: What's Next? How to take your Oracle to .NET experience to the next level.

By Jonathan Bruce 12/22/2009 #Microsoft has put developers on notice that it is deprecating the ADO.NET provider for #Oracle shipped with the .NET Framework: System.Data.OracleClient (OracleClient) as of .NET 4, expected in 2010. This means that Microsoft has decided to drop development of OracleClient from its ADO.NET roadmap; while the provider remains available, use of it should be avoided in new applications accessing Oracle data sources.