Silent period

As you probably know by now, i joined morgan stanley last monday. The work is really interesting, and I would lie if I was to tell you i'm not already learning at a much faster pace than usual.

But as you can probably see, my blogging is less frequent. Why? Less time of course, although plenty of side projects are still running. The main reason is that I'd like to focus on blogging about some of the great stuff we're doing. After looking for a long time, on google and other search engines, I didn't find any other official morgan stanley bloggers. Why? Are you out there?

The point is, before i can feel confident about my blogging, I need to see where I stand and where my company stands. This takes time, and hopefully we'll get there. In the meantime, I'll post a bit less. But if you're a morgan stanley employee wanting to start a blog, internally or on the web, or if you already blog, please contact me. I'm not disclosing too much by saying that exciting things could happen. So contact me, lamblas on our corporate intranet, and lamblas on jam.

And of course, if you wanna join morgan stanley as a developer, architect, infrastructure guy or whatever, please come to me. My email is still


Lookin for a new C# job?

Are you an experienced highly technical C# developer?

If you are, let me know, as my agency is looking for people to place into highly rated companies with great salaries. They did a great job for me, they can do a great job for you. So if you want to be placed in a very successful company, just forward me your cv by email, sebastien.lambla AT, and you could be just minutes away from your dream job!

Don't you think i should've been a marketing guy?


myApp.vshost.exe or when Visual Studio wanna be funky

JC asks what this new funky myAppName.vshost.exe is created at the same time as myAppName.exe… Well, this is used for debugger support. If you look at the content of that file, what you will see is mostly a dumb assembly containing only the following:

public static void Main(string[]
      HostProc proc1 = VsHostAppDomainManager.HostProcListener; 


What this does is simply use the new hosting model by using the VsHostAppDomainManager class in vshostutil.dll, which you can find in c:\program files\Microsoft Visual Studio 8\Common7\IDE. It inherit from the new System.AppDomainManager in mscorlib.dll. It obviously controls the security settings (letting you run your debug code in any trust level you want) and other nifty things, including redirecting the console input and output to the nice little Console window in visual studio.

A confirmation here. Once again brought to you first by the technologist :-)