SP1, as far as I can tell, introduced a bug wherein applications that had specific code groups granting them permissions with a membership determined by a strong key could not run when launched via the href-exe/moble code technique. Keith Brown did some spelunking and determined that ieexec.exe (the hosting process for such an app) would (mistakenly?) require that code from the site as a whole had at least Execution permissions before taking any of the other permissions for the specific assembly into account. The upshot is that to let wahoo.exe run on a .NET SP1+ box, you had to have two code groups, one that gave Internet permissions or greater to assemblies w/ a strong name and one that awarded at least Execution permission to all assemblies from sellsbrothers.com. I've updated the Wahoo! site w/ an MSI that creates both of these code groups along with the full source so that you can do the same for your own assemblies. Enjoy!
Here. "We still get people saying to us, 'What is .Net?'" Gates said at a conference held two weeks ago specifically to answer that question. "It's one of those great questions that people can say, 'Yes, it's come into focus at the infrastructure level,' but a little bit where we go beyond that has been unclear to people."
You’d have thought they would have learned their lesson from COM, OLE and ActiveX before this. I guess the slack caused by the Internet boom has taught even Microsoft bad habits.
Here. From Jim Wilson: The .NET CF Resource site has been substantially updated and we now have the discussion group online.
If you have a questions about the .NET Compact Framework, information that you would like to share or you just want to see what other people are doing with the .NET Compact Framework, this is the list for you.
