Would you like to try writing a marshal_as<> specialization? They're super simple, after all. Here's a list of some that we're sure to need:

Array Conversions

Other Conversions:

I've pasted the table in as I received it, and linked to things we already have. I'd like to come back to this list and add links as you send me things.

Kate

From Jason Olson.

//code starts here

#pragma once
#include <msclr\marshal.h>
#include <msclr\marshal_windows.h>

namespace msclr {
namespace interop {

//code ends here

At first glance the pin_ptr is a little scary, but this code doesn't return it, it dereferences it. So no "GC hole" to worry about.

Kate

From Jason Olson.

//code starts here

#pragma once
#include <msclr\marshal.h>
#include <msclr\marshal_windows.h>
namespace msclr {
namespace interop {

////////////////////////////////////////////////////////////////////
// File I/O Conversions (constants from System::IO)
///////////////////////////////////////////////////////////////////

template<>
inline DWORD marshal_as<DWORD, System::IO::FileMode>(const System::IO::FileMode& from) {

if (from != System::IO::FileMode::Append)
    return (DWORD)from;
else
    return (DWORD)System::IO::FileMode::OpenOrCreate;

template<>
inline DWORD marshal_as<DWORD, System::IO::FileAccess>(const System::IO::FileAccess& from) {
if (from == System::IO::FileAccess::Read)
    return GENERIC_READ;
else
    return GENERIC_WRITE;

template<>
inline DWORD marshal_as<DWORD, System::IO::FileShare>(const System::IO::FileShare& from) {
    return (DWORD)from;

//code ends here

Nice and simple.

Kate

Here we are!

What's going on here? Think pinvoke.net for the marshaling library. Send me your specializations (my email address isn't hard to find, or comment on this post -- if I use comments I'll remove them from here as I go) and I'll post them, one post per specialization, after the barest of quality control (I might make sure your code compiles) and then others can find them and comment on them. Together we will build a full-size marshaling library for all the common structs and classes that might pass back and forth across the managed-native boundary.

Some of you may have some specializations already written. Great! I'll post them as I get them and if I can't keep up, I have a volunteer team waiting to help. So let's go!

Kate Gregory