c++-cli

Ok, basically there is a large C++ project (Recast) that I want to wrap so that I can use it in my C# project. I've been trying to do this for a while now, and this is what I have so far. I'm using C++/CLI to wrap the classes that I need so that I can use them in C#. However, there are a ton of structs and enums that I will also need in my C# project. So how do I wrap these? The basic method I'm using right now is adding dllexport calls to native c++ code, compiling to a dll/lib, adding this lib to my C++/CLI project and importing the c++ headers, then compiling the CLI project into a dll,

I have my C++/CLI code using arrays like this (for example): array<String^>^ GetColNames() { vector<string> vec = impl->getColNames(); array<String^>^ arr = gcnew array<String^>(vec.size()); for (int i = 0; i < vec.size(); i++) { arr[i] = strConvert(vec[i]); } return arr; } It's compiling fine until I add the library "array" to the project: #include <array> Then I don't know how to use the managed CLI array, because the compiler thinks that all the declared arrays are the std::array . Errors examples: array<String^>^ arr // ^ Error here: "too few arguments for class template "std::array""

I'm Windows developer, I'm using Microsoft visual studio 2008 SP1. My developer machine is 64 bit. The software I'm currently working on is managed .exe written in C#. Unfortunately, I was unable to solve the whole problem solely in C#. That's why I also developed a small managed DLL in C++/CLI. Both projects are in the same solution. My C# .exe build target is "Any CPU". When my C++ DLL build target is "x86", the DLL is not loaded. As far as I understood when I googled, the reason is C++/CLI language, unlike other .NET languages, compiles to the native code, not managed code. I switched the C

Our project structure is like, native.dll :- This contains pure native code written in c\c++. This native.dll exposes some functions using *def file. Wrapper Library(wrapper.dll compiled with .Net framework v4.0) :- In order to use functionality of native.dll , a Wrapper lib(wrapper.dll) is written in C++\CLI using :clr\oldsyntax . This wrapper has all code of Interoperability and Marshalling . Application(Console App v4.0) directly uses wrapper.dll to use functionality provided by native.dll . Now this project needs to run in .Net Core . This means we will have an .Net Core application that

I had the code: std::string st = "SomeText"; ... std::cout << st; and that worked fine. But now my team wants to move to wstring . So I tried: std::wstring st = "SomeText"; ... std::cout << st; but this gave me a compilation error: Error 1 error C2664: 'std::basic_string<_Elem,_Traits,_Ax>::basic_string(const std::basic_string<_Elem,_Traits,_Ax> &)' : cannot convert parameter 1 from 'const char [8]' to 'const std::basic_string<_Elem,_Traits,_Ax> &' D:...\TestModule1.cpp 28 1 TestModule1 After searching the web I read that I should define it as: std::wstring st = L"SomeText"; // Notice the "L"

In C#, passing by reference is: void MyFunction(ref Dog dog) But in C++/CLI code examples I have seen so far, there is no use of ref but instead ^ symbol is used: void MyFunction(Dog ^ dog) Is the use of ^ symbol a direct replacement for ref when parameter passing? or does it have some other meaning I'm not aware of? Additional Question: I also see a lot of: Dog ^ myDog = gcnew Dog(); It looks like it's used like * (pointer) in C++.. Does it work similarly? Thanks! If Dog is a reference type ( class in C#) then the C++/CLI equivalent is: void MyFunction(Dog^% dog) If Dog is a value type (

I'm a bit rusty, actually really rusty with my C++. Haven't touched it since Freshman year of college so it's been a while. Anyway, I'm doing the reverse of what most people do. Calling C# code from C++. I've done some research online and it seems like I need to create some managed C++ to form a bridge. Use __declspec(dllexport) and then create a dll from that and use the whole thing as a wrapper. But my problem is - I'm really having a hard time finding examples. I found some basic stuff where someone wanted to use the C# version to String.ToUpper() but that was VERY basic and was only a