>>>God I love this business. For the first time I am doing what they said you could do in .NET but I've never done or seen done before - two languages in the same solution.
>>>
>>>And one of them is C++. Really a new experience. I am studying VC++ as fast as I can and trying to catch on to the whole Linking/compiling universe it inhabits and just where everything goes if using the VS2010 IDE (using VS2012 is not an option for this particular project as it just complicates the C++ side)
>>>
>>>Using Boost 1.54 and a whole lot of other stuff I'd never heard of as of July 4.
>>>
>>>I am going to be using QuickFAST (an opensource C++ project with a dotnet wrapper that decodes and deserializes feeds from financial markets that use the FAST/FIX protocol) and it isan adventure.
>>>
>>>Since I'm on the UT a lot I thought I check to see if we had any VC++ gurus in the house and if posting questions here was going to be useful. ( I also hang out on Stackoverflow, of course and QuickFAST has a very nice Google group)
>>>
>>>Now I think I should see if there is VC++ section of UT that I've just alwasy had turned off...
>>>
>>>(UPDATE - found the forum but it looks like no one is home)
>>
>>I gather Rick Hodgin is fluent in C/C++, dunno about VC++.
>
>I'm reading up on it now and it seems that unlike native (ISO standard) C++ the C++\CLI is managed code and has some advantages in security, stability and stuff like garbage collection. I am not quite sure where I code I'm using in the QuickFAST thing fits in but given that it was orginally written for a C++ world I suspect a lot of it is native C++. I have also heard that a big consideration is performance degradation when passing through the wall between unmanaged and managed code. Much to learn.
>
>Al, do you do C++\CLI in VS?

Nope.

ISTR years ago in the .Net 1.0 days I read an overview/position paper (from MS?) that touted C++ in .Net for leveraging an existing C++ code base.

I may be OTL about this but it looks like trying to get C++ to work with .Net has always been kludgy at best i.e. "Managed Extensions for C++" ( https://en.wikipedia.org/wiki/Managed_Extensions_for_C%2B%2B ) morphing into "C++/CLI" ( https://en.wikipedia.org/wiki/C%2B%2B/CLI ).

From the latter link (emphasis mine): "C++/CLI should be thought of as a language of its own (with a new set of keywords, for example), instead of the C++ superset-oriented Managed C++ (MC++) (whose non-standard keywords were styled like __gc or __value). Because of this, there are some major syntactic changes, especially related to the elimination of ambiguous identifiers and the addition of .NET-specific features.

Many conflicting syntaxes, such as the multiple versions of operator new() in MC++ have been split: in C++/CLI, .NET reference types are created with the new keyword gcnew. Also, C++/CLI has introduced the concept of generics (conceptually similar to standard C++ templates, but quite different in their implementation)."

Happy, happy, joy, joy.

Hopefully your favourite training company can help...