New beta version of NET CF (version 3.5)

**ImCoKeMaN** · #1 (**permalink**) 02-19-2007, 09:55 PM

I couldn't find this cab anywhere, but i read about it so i downloaded the entire ~6 gigs of "orcas" virtual PC images to get this. I was hoping it would fix the live search contacts issue, but it didn't seem to do that for me. You are all welcome to try however and feel free to make an OEM if ya like this.

**colonel** · #2 (**permalink**) 02-19-2007, 10:01 PM

All of these file names are shortened. Do you know if the two files that we know are causing issues are in this group?

**ImCoKeMaN** · #3 (**permalink**) 02-19-2007, 10:21 PM

Well it didn't seem to fix the issues we were having. i'm not the biggest fan of the net CF 2 so i'm not sure if this one is faster or anything yet either. I just figured that this was worth taking a look at.

**colonel** · #4 (**permalink**) 02-19-2007, 10:33 PM

Specifically, I am talking about:
GAC_Microsoft.WindowsMobile.PocketOutlook_v1_0_0_0 .dll
GAC_Microsoft.WindowsMobile.Status_v1_0_0_0.dll

These two files have either a link to the issues or the registries including them are the problem. The "Status" dll is the one in the error messages for IDTransfer. From what I have been able to find, neither are included in any .Net CF package. This leads me to believe that the files that are in the 3.5 kitchen are either incompatible with the OS or the registry has some issues in it.

**ImCoKeMaN** · #5 (**permalink**) 02-19-2007, 10:47 PM

Well here's the error i get:

Code:

2/19/07 8:52:11 PM
Version: 1.0.2592.31374
System.TypeLoadException: File or assembly name 'Microsoft.WindowsMobile.PocketOutlook, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35', or one of its dependencies, was not found.
   at System.Windows.Forms.Control.OnMouseDown(MouseEventArgs e)
   at Microsoft.Search.Mobile.LinkLabel.OnMouseDown(MouseEventArgs e)
   at System.Windows.Forms.Control.WnProc(WM wm, Int32 wParam, Int32 lParam)
   at System.Windows.Forms.Control._InternalWnProc(WM wm, Int32 wParam, Int32 lParam)
   at Microsoft.AGL.Forms.EVL.EnterModalDialog(IntPtr hwnModal)
   at System.Windows.Forms.Form.ShowDialog()
   at Microsoft.Search.Mobile.Flow.Forward(View view)
   at Microsoft.Search.Mobile.Controller.ChooseLocation()
   at Microsoft.Search.Mobile.DirectionsView.ChooseLocation(ComboBox thisList, ComboBox otherList)
   at Microsoft.Search.Mobile.DirectionsView.ChooseStartLocation()
   at Microsoft.Search.Mobile.DirectionsView.linkStart_MouseDown(Object sender, MouseEventArgs args)
   at System.Windows.Forms.Control.OnMouseDown(MouseEventArgs e)
   at Microsoft.Search.Mobile.LinkLabel.OnMouseDown(MouseEventArgs e)
   at System.Windows.Forms.Control.WnProc(WM wm, Int32 wParam, Int32 lParam)
   at System.Windows.Forms.Control._InternalWnProc(WM wm, Int32 wParam, Int32 lParam)
   at Microsoft.AGL.Forms.EVL.EnterModalDialog(IntPtr hwnModal)
   at System.Windows.Forms.Form.ShowDialog()
   at Microsoft.Search.Mobile.Flow.Forward(View view)
   at Microsoft.Search.Mobile.Controller.Directions(Location start, Location destination)
   at Microsoft.Search.Mobile.MainView.Directions()
   at Microsoft.Search.Mobile.MainView.iconDirections_MouseDown(Object sender, MouseEventArgs e)
   at System.Windows.Forms.Control.OnMouseDown(MouseEventArgs e)
   at System.Windows.Forms.Control.WnProc(WM wm, Int32 wParam, Int32 lParam)
   at System.Windows.Forms.Control._InternalWnProc(WM wm, Int32 wParam, Int32 lParam)
   at Microsoft.AGL.Forms.EVL.EnterMainLoop(IntPtr hwnMain)
   at System.Windows.Forms.Application.Run(Form fm)
   at Microsoft.Search.Mobile.Controller.Run(View main)
   at Microsoft.Search.Mobile.MainView.DoMain()
   at Microsoft.Search.Mobile.MainView.Main()

The System.Windows.Forms dll is included in 3.5 and is mentioned in this error file so i'm thinking that could be part of the issue, but clearly not conclusive at this point. It still seems like there should be a new version of the pocketoutlook.dll or something somewhere.

**colonel** · #6 (**permalink**) 02-19-2007, 10:55 PM

Try to run IDTransfer if you want. You will get almost the same error except for there is not nearly as much detail. However, the main error is the same. Perhaps we should try to track down a forum where users have an official 3.5 release and see if they are having the same issues. That would at least let us know if it is a true 3.5 issue or an issue with our 3.5 in the kitchen.

Sogarth · #7 (**permalink**) 02-19-2007, 10:58 PM

This could be a bit tricky, seeing as how there aren't that many officially released WM5 AKU 3.5 ROMs out there. Most of the current AKU 3.5 ROMs have been based off of Helmi's release, which (according to this xda-dev wiki page) he (indirectly) got from a Benq P51. Anybody know anybody with a Benq P51?