clr

I think I've known the answer for a class, just want to confirm my understanding is correct. Let's say I have a ClassA and its instance named a . When a.MethodA() is invoked: (1) CLR find the type of ClassA by the type pointer of a in the heap(the type have been loaded into the heap) (2) Find the MethodA in the type, if not found, go to its base type, until the object class. Maybe my understanding is not quite precise, but I think it's basicly correct(Correct me if it's wrong!). And here comes the question of a simple struct . struct MyStruct { public void MethodA() { } } I have var x = new

Is there any way to put spaces in a C# enum constant? I've read that you can do it in VB by doing this: Public Enum EnumWithSpaces ConstantWithoutSpaces [Constant With Spaces] End Enum ...and then access it like this: Public Sub UsingEnumWithSpaces() Dim foo As EnumWithSpaces = EnumWithSpaces.[Constant With Spaces] End Sub That implies to me that the CLR can handle an enum with spaces. Is there any way to do this in C#? Joel Marcey This blog post might help you: http://blog.spontaneouspublicity.com/2008/01/17/associating-strings-with-enums-in-c/ From the article: But enums can't have spaces in

I have an instrument that stores timestamps the microsecond level, and I need to store those timestamps as part of collecting information from the instrument. Note that I do not need to generate timestamps ; these time stamps are pre-generated by the instrument itself using a high resolution real-time operating system. Parsing out these values is not an issue — they are stored using a standard format in UTC time. Originally I wanted to use the C# DateTime structure can only store time stamps up millisecond resolution. Is there another object supplied with .NET or a common C# library that

I am trying to create a pure MSIL assembly from a C++/CLI project using /clr:pure and /clrimagetype:pure flags, however, the output assembly specifically targets x86. Am I missing anything that might be preventing my project to be compiled as MSIL only? Glenn Slayden You can create an AnyCPU dll with C++/CLI , but in the simplest case, you will not be able to use MFC, ATL or the CRT. However, if you just want to write pure managed .NET code in C++/CLI, including managed pointers (which /clr:safe does not allow), and get the more elaborate code optimization of the C++/CLI compiler, read on: For

How to call managed c# functions from unmanaged c++ Or use a project of mine that allows C# to create unmanaged exports. Those can be consumed as if they were written in a native language. I used COM interop first, but by now I switched to IJW (it just works), as it is a lot simpler. I have a wrapper C++/CLR DLL (compile with /clr). A simple example (using statics to make the calls easier): namespace MyClasses { public class MyClass { public static void DoSomething() { MessageBox.Show("Hello World"); } } } In the DLL I can reference namespaces as follows: using namespace MyClasses; And call it

As I understand it I can use reverse P/Invoke to call C# from C++. Reverse P/Invoke is simply a case of: Create you managed (c#) class. Create a c++/cli (formerly managed c++) class library project. Use this to call the managed c# class (presumably via a reference). Call the c++/cli code from native c++. Questions: Is this correct? Is the DLL created at step 2 known as a mixed mode DLL? Has C++/CLI completely superseded Managed C++ as far as MS are concerned? Is COM completely avoided using this approach? At what point would the CLR be created and run, and by whom? Thanks in advance Aamir Here