Jon Westfall
10-21-2005, 02:00 PM
<div class='os_post_top_link'><a href='https://blogs.msdn.com/netcfteam/archive/2005/10/11/479793.aspx' target='_blank'>https://blogs.msdn.com/netcfteam/ar.../11/479793.aspx</a><br /><br /></div><i>"Just like other Windows CE applications, .Net Compact Framework V2 (NETCF V2) is distributed as a set of CAB files. This article describes these CABs and discusses potential installation problems as well as ways to solve these problems. ... Each CAB file contains at least one native (CPU dependent) NETCF runtime, CPU independent managed libraries and setup DLL. In some cases CAB file contains more than one native runtimes, each optimized for particular CPU flavor. For example, NETCFv2.wce5.mipsii.cab contains two runtimes, one for MIPS II CPU and another one for MIPS II FP CPU (which has dedicated floating point unit). Correct runtime files are picked at installation time by setup DLL, unused files are discarded to save space."</i><br /><br />If the .NET Compact Framework cab files are a bit of a mystery to you (Which would be bad if you intend on building an application dependent on CF...), then this piece originally highlighted by our sister site, Smartphone Thoughts, can give you the lowdown on their usage. Happy Developing!