Contact person: Business Client

Phone:Show

Email:Show

Location: Perth, Australia

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I am building a Windows-only desktop application whose main focus is the user interface, yet parts of the core logic are already written in C++. I now need clear, practical guidance on how to let my existing C++ modules talk to new C# UI components so that data moves back and forth seamlessly without marshalling headaches or awkward latency.

What I want from you is a working strategy for clean, maintainable interop—whether that ends up being C++/CLI, p/Invoke, COM, or another approach you can justify for this scenario. You should be comfortable profiling and explaining the data-exchange costs of each option and showing me how to keep memory management predictable on both sides of the boundary.

Deliverables I expect:
• A short technical session (call or screen share) where you walk me through the recommended architecture
• A minimal but complete proof-of-concept project demonstrating the techniques on Windows (visual project files included)
• Concise notes or code comments that document the key decisions, pitfalls to avoid, and next steps for scaling the solution

If you have shipped Windows desktop software that blends C++ back-ends with C# front-ends and can explain the trade-offs in plain language, I would love to work with you." (client-provided description)