clr

I'm thinking of rewriting a brand new VB.NET application in VB 6. The application runs under terminal services and makes heavy use of COM. For some reason, there is random weirdness with the application - Random Access Violation errors (WinDbg exception analysis points into dll's like comdlg32.dll, mscorwks) Random Buffer Overflow errors (same) Random errors in general - for example this line in Form.Load sometimes throws - Me.Icon = Resources.MyIcon I have followed all possible advice concerning resources, garbage collection, disposal patterns, etc... It just doesn't seem to do any good. I'm

I need to dynamically create a .NET 2.0 compatible assembly from within my .NET 4.0 process. Currently it is achieved with this: AssemblyBuilder ab = AppDomain.CurrentDomain.DefineDynamicAssembly(...) ModuleBuilder mb = assemblyBuilder.DefineDynamicModule(...); But unfortuntely all dll's produced are .NET 4.0 (inherited from my 4.0 process) which doesn't work with my other .NET 2.0 processes. Any idea how 2 different CLR versioned AppDomains can co-exist in the same process? Have a look at this question: http://social.msdn.microsoft.com/Forums/en/clr/thread/1bfd7f40-fd57-4c9f-803f-aa4b19214af9

Can anyone explain how the CLR handles Static classes? Does the CLR create one singleton instance for handling static classes internally? If not, why do we have a static constructor in C#? (Per my understanding, we use constructors only for instantiating the class) Sriram Sakthivel First of all there is no static class in CLR. CLR doesn't know anything about static class. It is the feature of C#. Static classes are compiled into abstract as well as sealed class. Making it abstract prevent instantiation of it and sealed prevents inheritance. Static classes are no special, it is just a simple

What is the use of IL file generated from .NET (using MSIL assembler- ilasm.exe)? I read it from http://msdn.microsoft.com/en-us/library/496e4ekx.aspx but i am not sure about the use of IL file generated from .NET (using MSIL assembler- ilasm.exe). Can any one explain me? You might want to use IL directly in those (admittedly rare) situations when a higher level language like C# doesn't provide the precision or features you need. For instance, there are some features in System.Dynamic that are used from the dynamic languages such as IronPython that can't easily be used in C#. Going straight to

I have an application hosting the .net clr with a custom AppDomain Manager and an AssemblyManager with a store. This all works fine when the Assembly with the AppDomainManager in is a dll in the same directory as the executable. What I want to do is embed the Managers assembly inside the executable. When I do this ProvideAssembly is called with the correct strong name, I return a stream with the assembly bytes, but ICLRRuntimeHost->Start() returns an error indicating that a type cannot be loaded. All the assembly binding details match etc. My questions is, does anyone know if this

I've googled around a bit, and I haven't been able to find a good listing of what classes from the .net CLR are not included in the 'CoreCLR' aka Silverlight. What is Silverlight missing from the Windows .net Framework? Also, is there anything that the Silverlight runtime has that the .net Framework doesn't? Silverlight Runtime (Silverlight CLR) is essentially a mini-mini CLR :). Microsoft did the work of removing many dependencies to .NET Framework assemblies not part of the Silverlight release Silverlight CLR is a subset of the .NET Framework that contains components and libraries, including