I want to sign an assembly but it is refering to an assembly,
Interop.MSForms, which is unsigned assembly. Hence, I'm getting compilation
error. Can anyone suggest a way out? Is there any way by which we can remove
the restriction that referred assemblies should be always ...

I need help with a couple of questions, I have create and structure like:
Structure byteArray
Public byteA() As Byte
End Structure

I'm on Windows XP 64 bits and I have a 32 bits .NET assembly which was
compiled without the 32BIT flag, I cannot use corflags to add it because it
is signed and it is not mine. Is there a way in the config file to say it
has to be run in 32 bits mode instead of 64 bits mode?

I suspect I have some memory leaks in a .NET Application wrote with VStudio
2005 final.
I want to debug it using CLR Profiler but I didn't found a version that
works with final version of .NET framework (Whidbey).

Hello.  I am trying to profile a service using CLR Profiler.  It seems
to work just fine if I start CLR Profiler through the GUI, but the
default value of OMV_PATH=c:/Windows/Temp (where the log files are
written) is on a quite small partition.

...both have constructors that take two strings:
ArgumentException(string message, string paramName)
ArgumentNullException(string paramName, string message)
This swap of arguments does not make any sense. What kind of quality control

All -
This might be a purist question, but i want to convince my handler with a
reasonable argument.
Lets say i have an object *internal* to my assembly (InternalMyObject) and

I want to instantiate a class at runtime that accepts a parameter, but I am
currently using Assembly.LoadFrom so I am having to do without the parameter.
Assembly.LoadFrom doesn't seems to support parameterized constructors (which
isn't a suprise, really) but it there another way ...

Hello Team..
No, I am not posting in the wrong forum :).
I meant to check if the MS pros have read/heard of anything about
Oracle Lite 10R2 and its support for .Net Stored Procedure..

I have been looking into the claim that the keyword lock is not safe
when exceptions are possible. That lead me to try the following code,
which I think has uncovered a serious error in the .NET 2.0 framework.
Note that this runs better, but not perfectly, on .NET 1.1.