0 Replies Latest reply on Sep 12, 2013 10:47 AM by Vadim Rapp

    Symbol assemblies depend on .Net CF 2.0

    Vadim Rapp

      In Visual Studio 2008 we have developed an application for Windows Mobile 6 using .Net CF 3.5, using EMDK 2.8.  The application includes references to symbol.dll and symbol.barcode.dll.  When we build smart device setup project for it, the following warnings show up:

       

      Warning    1    Unable to find dependency 'Microsoft.WindowsCE.Forms' (Signature='969DB8053D3322AC' Version='2.0.0.0') of assembly 'Symbol.dll'

      Warning    2    Unable to find dependency 'System.Windows.Forms' (Signature='969DB8053D3322AC' Version='2.0.0.0') of assembly 'Symbol.dll'

      Warning    3    Unable to find dependency 'mscorlib' (Signature='969DB8053D3322AC' Version='2.0.0.0') of assembly 'Symbol.dll'  

      Warning    4    Unable to find dependency 'mscorlib' (Signature='969DB8053D3322AC' Version='2.0.0.0') of assembly 'Symbol.Barcode.dll'  Warning    5    Unable to find dependency 'System.Windows.Forms' (Signature='969DB8053D3322AC' Version='2.0.0.0') of assembly 'Symbol.Barcode.dll'

      Warning    6    Unable to find dependency 'System' (Signature='969DB8053D3322AC' Version='2.0.0.0') of assembly 'Symbol.Barcode.dll'

       

      If I'm not mistaken, it means that these assemblies depend on .Net CF 2.0, rather than 3.5. We don't see any negative consequences, the deployed application works OK, but still wondering, is this expected? The documentation mentions that EMDK supports .Net CF 3.5 as well, so maybe there's some way to make these assemblies dependent on 3.5 ?