C# – what is this oleaut32.dll

cnet

we had an error encountered on one of our windows service application, that points to this dll – oleaut32.dll

here's the eventviewer logs

The description for Event ID 1000 from source .NET Runtime 4.0 Error
Reporting cannot be found. Either the component that raises this event
is not installed on your local computer or the installation is
corrupted. You can install or repair the component on the local
computer.

If the event originated on another computer, the display information
had to be saved with the event.

The following information was included with the event:
> [our-application].exe
> 4.0.0.0 5174a88d oleaut32.dll
> 5.2.3790.4807 4d0fa719 0 0000000000024057

we are not sure how or why did this happened unexpectedly or what's causing this error. also, we haven't encountered this kind of error before.

our application is using .net framework 4.0 and runs on a windows 2003 server with updated Microsoft security patches.

Best Answer

oleaut32.dll it's a library used in Microsoft for OLE technologies; OLE Automation

You could check Microsoft to see if you find any support.

Another link with alternatives is this.

consider this:

Important: Do not download oleaut32.dll from a "DLL download" website. There are many reasons why downloading a DLL file is a bad idea. If you need a copy of oleaut32.dll, it's best to obtain it from its original, legitimate source.

This is the style that Microsoft tends to use in their examples.

It appears that the guidance in this area may have changed, as StyleCop now enforces the use of the C# specific aliases.

C# – the difference between const and readonly in C#

Apart from the apparent difference of

having to declare the value at the time of a definition for a const VS readonly values can be computed dynamically but need to be assigned before the constructor exits.. after that it is frozen.
const's are implicitly static. You use a ClassName.ConstantName notation to access them.

There is a subtle difference. Consider a class defined in AssemblyA.

public class Const_V_Readonly
{
  public const int I_CONST_VALUE = 2;
  public readonly int I_RO_VALUE;
  public Const_V_Readonly()
  {
     I_RO_VALUE = 3;
  }
}

AssemblyB references AssemblyA and uses these values in code. When this is compiled:

in the case of the const value, it is like a find-replace. The value 2 is 'baked into' the AssemblyB's IL. This means that if tomorrow I update I_CONST_VALUE to 20, AssemblyB would still have 2 till I recompile it.
in the case of the readonly value, it is like a ref to a memory location. The value is not baked into AssemblyB's IL. This means that if the memory location is updated, AssemblyB gets the new value without recompilation. So if I_RO_VALUE is updated to 30, you only need to build AssemblyA and all clients do not need to be recompiled.

So if you are confident that the value of the constant won't change, use a const.

public const int CM_IN_A_METER = 100;

But if you have a constant that may change (e.g. w.r.t. precision).. or when in doubt, use a readonly.

public readonly float PI = 3.14;

Update: Aku needs to get a mention because he pointed this out first. Also I need to plug where I learned this: Effective C# - Bill Wagner

Best Answer

Related Solutions

C# – the difference between String and string in C#

This is the style that Microsoft tends to use in their examples.

C# – the difference between const and readonly in C#

Related Topic