clr

I have a big and bloated software and I want to add a new GUI element to it. The GUI element was written using XAML and WPF. I created the UI element in a separate assembly, and reference it in the big software. The two projects compiled smoothly under VS2010, but when I run my application I get a TypeLoadException . Looking into the exception with the debugger, I get the following message : Could not load type GUI.Dashboard from assembly GUI, blah, blah . There is no InnerException nor any further detail. The .GNU documentation says that this message appears when there is no message passed to

Can I call a dll from a stored procedure using the open connection? I have a dll that gets data from SQL Server and I don't want to open a new connection when I call it from the stored procedure. Thank you Here is an exemple public class Class1 { public static SqlString GetName(SqlString str) { SqlCommand cmd = new SqlCommand(str.ToString()); cmd.CommandType = System.Data.CommandType.Text; string name = cmd.ExecuteScalar().ToString(); return name; } } and this is the SQL code CREATE FUNCTION fn_TestConnection ( @str nvarchar(255) ) RETURNS nvarchar(max) AS EXTERNAL NAME TestConnection.

Can we compile C library as .Net dll (containing and opening access to all C libs functions) by just compiling cpp project containing code like extern "C" { #include <library.h> } with /clr:pure argument with VS? (VS10) Or we should do something more trickey? I found it is the best to use the old style Managed C++ for this. CLR:PURE just wont cut it. Example: extern "C" int _foo(int bar) { return bar; } namespace Bar { public __gc class Foo { public: Foo() {} static int foo(int bar) { return _foo(bar); } }; }; Compile with: /clr:oldSyntax Now you can reference the assebmly, and call Bar.Foo

When doing an upcast or downcast, what does really happen behind the scenes? I had the idea that when doing something as: string myString = "abc"; object myObject = myString; string myStringBack = (string)myObject; the cast in the last line would have as only purpose tell the compiler we are safe we are not doing anything wrong. So, I had the idea that actually no casting code would be embedded in the code itself. It seems I was wrong: .maxstack 1 .locals init ( [0] string myString, [1] object myObject, [2] string myStringBack) L_0000: nop L_0001: ldstr "abc" L_0006: stloc.0 L_0007: ldloc.0 L

According to the Microsoft documentation, when an unhandled exception occurs on a thread (from either the thread pool or created using the System.Threading.Thread class) the AppDomain.UnhandledException event should fire for the default AppDomain of the application. Here is the MSDN link which explains it after the second NOTE section. But I cannot reproduce this behaviour, as far as I can tell from my test application it never fires the UnhandledException on either the default AppDomain or the AppDomain used to create the thread. Is the documentation wrong or my testing code? using System;

As a learning exercise I'm writing myself a simple extension / plugin / macro framework using IronPython - I've gotten the basics working but I'd like to add some basic debugging support to make my script editor easier to work with. I've been hunting around on the internet a bit and I've found a couple of good resources on writing managed debuggers (including Mike Stall's excellent .Net Debugging blog and the MSDN documentaiton on the CLR Debugging API ) - I understand that IronPython is essentially IL however apart from that I'm a tad lost on how to get started, in particular: Are there any