Chris
Fri Jul 18 08:38:57 CDT 2008
Compile != run. The CF doesn't support all of the opcodes that managed C++
creates, so compile all you want, the CLR can't interpret all o the IL and
trying to run may fail. I say "may" becassue it's quite possible to create
a simple app in managed C++ that doesn't contain unsupported opcodes, but
there's no way to prevent it, so you will undoubtedly get to a point in any
real-world application where the opcode is used and the app will not work.
--
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com
"superclass" <superclass@discussions.microsoft.com> wrote in message
news:9EE489F9-D23E-4A3D-9B6A-49F30ABB5D50@microsoft.com...
>
>
> "Christopher Fairbairn [MVP]" wrote:
>
>> Hi,
>>
>> "superclass" <superclass@discussions.microsoft.com> wrote in message
>> news:8D88CD5E-426A-428A-8909-F594B85964E7@microsoft.com...
>> > use #pragma managed/#pragma unmanaged in your C++ program(cpp) file.
>> > in managed block you can make a function that do your .NET CF and then
>> > call this function from unmanaged code.
>>
>> Managed C++ is not a supported language for the .NET Compact Framework.
>> So
>> this solution will not work.
>>
>
> so why I can still compile program with managed/umanaged code with Visual
> Device Compiler??
>
>
>