Folks -
I am observing some weird behavior in our application during shutdown, let
me see if I can explain this clearly.
Lets say I open 2 instances - A and B - of the application on my machine.

I've seen the following being explained about .NET applications in a C#
Microsoft Course :
"An assembly executable (exe) contains a small amount of unmanaged code,
known as the stub, which is used to load the .NET CLR and start execution of

I am having a problem with my VB .Net application. It runs fine on my machine on which I developed it on. When I run it on another person's machine, I get the following error
Application popup: ServiceDeskAdmin.exe - Common Language Runtime Debugging Services : Application has ...

I would like to know if the here below 'MyClass' is threadsafe. In other
word, is reference affectation an "atomic operation" for the CLR ?
class MyClass
{

We have an architecure in which we are having one Component server and other
Web Server which has components installed.
I want to use .NET remoting in that scenario, Please suggest me any solution
which has been worked out by anyone out there.

I have a DataAdapter that connects to this table.
Table1
Field1 unique int Identity
Field2 int

Has anyone ever run into a problem using resource files that results in the
following error message:
mscorlib.resources couldn't be found! Large parts of the BCL won't work!
I added an additional resource file to my project and load the resource into

This post is more to do with my curiosity than anything.
Does anyone know why the mscorlib public key is so short?
It is only 16 bytes long, and on top of that only has 1 byte that is
non-zero.

Look at the following code :
I instanciate a class which creates a new Thread in its .ctor.
Then i set the instance of this class to null and let the GC run -
but GC only cleans this instance up if I explicitly Start() and

We have a Delphi application that hosts .NET 1.0.  Some customers run it
from a Citrix server just fine, while others get error number 2147024894
when calling ICorRuntimeHost->Start
We are binding to the runtime with default values, and get back a valid

I am writing some code that uses the Profiling API.
I want to know if adding (or modifying if present) a Type Initializer
(.cctor) is a safe thing to do whilst profiling?
I intend to add it during the "AssemblyLoadFinished" profiler

I have made a program that works fine on my computer. When I try to run it on another computer I get the error message
Title: "MYPROGRAM.EXE -Common Language Runtime Debugging Services
Message: Application has generated an exception that could not be handled
Process id=0x550 (1360), ...

I have an application that uses a simple utility DLL. The DLL has a key
specified in AssemblyInfo file:
[assembly: AssemblyKeyFile(@"..\..\Utils.snk")]
Everything works fine on a development machine. Now when I try to install

I know there have been a lot of posts in relation to GC, working set,
trimming working sets, minimizing forms, etc. I've read every one I can
find, but have not found a solution to my problem. The closest I ever found
was the thread here recently "GC does not release memory... ...

I know that some calls into the COM profiler API can cause the CLR to call
back into your COM object as it loads in additional classes. I was wondering
if I could force this to happen for classes I want.
For example, I need to know certain facts about a method call (such as if it