Prev: Error 1 Post-deploy error 0x00000001
Next: Microsoft.VisualStudio.TestTools
From: sh on 29 Sep 2009 09:06
OK, I'm ready to live with the error message. But so far these
dependencies haven't caused me any problems. Do you think they might
cause some in the future?

If I run into some problem, I guess I'll just have to note that it might
be caused by these dependencies.

Thanks.

Chris Tacke, MVP wrote:
> You cannot consume a full framework assembly from a CF app. Period. So
> those "proprietary functions" in your full-framework library cannot be
> used as they are. That is the root of this problem, by adding the
> referfence to your assembly, it then pulls in the dependencies - which
> includes the desktop assemblies you're seeing the errors about.
>
>
From: Chris Tacke, MVP on 29 Sep 2009 09:52
Yes, they are going to cause a problem as soon as your code attempts to call
a method in a desktop-compiled assembly.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

"sh" <shamada(a)prupipe.com> wrote in message
news:keKdnf1-W5Lcm1_XnZ2dnUVZ_qCdnZ2d(a)earthlink.com...
> OK, I'm ready to live with the error message. But so far these
> dependencies haven't caused me any problems. Do you think they might cause
> some in the future?
>
> If I run into some problem, I guess I'll just have to note that it might
> be caused by these dependencies.
>
> Thanks.
>
> Chris Tacke, MVP wrote:
>> You cannot consume a full framework assembly from a CF app. Period. So
>> those "proprietary functions" in your full-framework library cannot be
>> used as they are. That is the root of this problem, by adding the
>> referfence to your assembly, it then pulls in the dependencies - which
>> includes the desktop assemblies you're seeing the errors about.
>>
First  |  Prev  | 
Pages: 1 2
Prev: Error 1 Post-deploy error 0x00000001
Next: Microsoft.VisualStudio.TestTools