Today I made some progress on my BooLanguage implementation in Visual Studio 2005, I hope I can release some early version later this week.
But today I will show you a important tip ZMan has already reported about here: Why do I get a 'Loader Lock' Error when debugging my Managed DirectX application
Very often when you try to debug your Managed DirectX application in Visual Studio 2005 you get this very annoying "Loader Lock" window when starting to debug your application. It is caused by the Managed DirectX for .NET 1.1 runtime while using .NET 2.0 of your project. Such a loader lock looks like this:
You can press F5 to continue, but if you get 3-4 of them every time you start your project it gets very annoying, especially because VS seems to lag very bad because of this windows.
To fix this just press Ctrl+D, +E (hold down Ctrl for both keys) and disable the LoaderLock exception to be thrown in the Managed Debugging Assistants category:
From now on enjoy your application to start immediatly instead of waiting around all day and pressing F5 like a mad man :)