CF 2.0 support on generic CE 4.2 devices

I just got word today from the Group Program Manager of the Compact Framework team that Compact Famework 2.0 Service Pack 1 (due out next year – dates not finalized, so I won’t speculate) will have the following support for general Windows CE 4.2:



  • Runtime support only
  • Supported for all WinCE processor types (i.e., not just ARM family)

The picture for integration into Studio 2005, debugging, emulators and all of that is still fuzzy, so for now I’d plan pessimistically and assume that the two points above are all you’ll get, but at least it lets you move forward.


 

Nonintuitive linker errors in Studio ’05

Yesterday I was working on a project using C++ for a device under Visual Studio ’05 and for some reason it stopped linking with the following error:


error LNK2019: unresolved external symbol __security_check_cookie referenced in function “int __cdecl RegisterAndActivate(void)” (?RegisterAndActivate@@YAHXZ)


No idea even what the error meant, so I messed with some settings, rolled back code – all the usual things to try to find it.  Nothing.  I decided to bag it for the night – maybe fresh eyes today would help.


I loaded the project again today.  Same error.  I removed the project from the solution, created a new one, and re-added my code. Same error.  So I turned to my fellow coders to see if anyone else had seen this.


Jeff Abraham of Microsoft replied as follows:



My psychic powers tell me that you are building against PPC2003, and you aren’t linking against secchk.lib. Try adding that to the linker inputs line, and seeing if that fixes the issue. I’m not sure how you would have gotten into this state without changing anything, as any project targeting PPC/SP 03 should have these libraries by default.


Sure, enough, I added secchk.lib to the Additional Dependencies line under the Project’s Linker | Input section and it’s now building again.  Why the error occured in the first place I’m not too concerned with – the release of Studio is only weeks away and I’ll be uninstalling soon, but Googling on this error turned up nothing helpful at all.  Hopefully this blog entry will remedy that if someone else is looking.