clr

I tried to print the CLR object/class by WinDbg, however it failed. Firstly, I tried to run x clr!Thread* to get some CLR class name, the output like below. 00007ffd`68957f18 clr!ThreadStore::s_pOSContext = <no type information> 00007ffd`685b0bf0 clr!ThreadNative::SetApartmentState (<no parameter info>) 00007ffd`685b12c0 clr!ThreadNative::YieldThread (<no parameter info>) 00007ffd`6806be60 clr!Thread::ResetManagedThreadObjectInCoopMode (<no parameter info>) 00007ffd`6895e928 clr!ThreadpoolMgr::LastCPThreadCreation = <no type information> 00007ffd`68627800 clr!ThreadPoolNative:

I want to convert System::String ^ to LPCWSTR . for FindFirstFile(LPCWSTR,WIN32_FIND_DATA); Please help. The easiest way to do this in C++/CLI is to use pin_ptr : #include <vcclr.h> void CallFindFirstFile(System::String^ s) { WIN32_FIND_DATA data; pin_ptr<const wchar_t> wname = PtrToStringChars(s); FindFirstFile(wname, &data); } To convert a System::String ot LPCWSTR in C++/CLI you can you use the Marshal::StringToHGlobalAnsi function to convert managed strings to unmanaged strings. System::String ^str = "Hello World"; IntPtr ptr = System::Runtime::InteropServices::Marshal::StringToHGlobalAnsi

This got a bit long-winded, so here's the quick version: Why does this cause a runtime TypeLoadException? (And should the compiler prevent me from doing it?) interface I { void Foo<T>(); } class C<T1> { public void Foo<T2>() where T2 : T1 { } } class D : C<System.Object>, I { } The exception occurs if you try to instantiate D. Longer, more exploratory version: Consider: interface I { void Foo<T>(); } class C<T1> { public void Foo<T2>() where T2 : T1 { } } class some_other_class { } class D : C<some_other_class>, I { } // compiler error CS0425 This is illegal because the type constraints on C

I have a (C#) function similar to the following. private static bool SpecialCase = false; public void Foo() { if (SpecialCase) { InternalMethod(); return; } Console.WriteLine(); } [MethodImpl(MethodImplOptions.InternalCall)] private static extern void InternalMethod(); When I execute this with the .NET Framework 4 inside the debugger, the method successfully prints blank line to the console and returns. When I execute it outside the debugger, it throws an exception with the following message: System.Security.SecurityException: ECall methods must be packaged into a system module. It appears the

CLR profiler does not seem to work with the Silverlight CLR. Does another memory profiler exist? Doesn't seem to be one available yet. However, as recommended in this forum thread , you can convert your Silverlight app to a WPF application and profile that: There is no tool as of now but as a workaround you can easily create a desktop (WPF) version of your Silverlight client from the same code base and few tweaks (refer Scot's blog for an example on this - http://weblogs.asp.net/scottgu/pages/silverlight-tutorial-part-8-creating-a-digg-desktop-application-using-wpf.aspx ) . Once you are done

I know that it is possible to have Nullable value types that wraps the value type and gives ability to store null. But is there a technical reason do not allow the value type to be null or the reason is only conceptual? A reference type is storeed as a reference (like a pointer) to an object instance. null means a reference that isn't pointing to an instance of an object. Value types are stored as the values themselves, without any references. Therefore, it doesn't make sense to have a null value type—the value type by definition contains a value. Nullable<T> is a value type with a HasValue