ANN: OpenNETCF SDF 1.4 Released

G

Guest

Hmmm... This is not good, unless it's "Monday morning syndrome":

Win32Window.FindWindow now returns type "Win32Window" instead of IntPtr.
But Win32Window.SetWindowPos expects "IntPtr" instead of "Win32Window".
CType cannot convert between the two.

I've reverted to Core.FindWindow which still returns an IntPtr....

Maybe there's just something I'm not seeing here.
 
G

Guest

There's are implicit operators for converting between IntPtr and Win32Window
and vice versa, so they're interchangeable now.

-Chris
 
G

Guest

How does that work exactly? This is what I have and VS.Net doesn't like it:

Dim hWnd As Win32Window
hWnd = Win32Window.FindWindow(Nothing, "MS_SIPBUTTON")
Win32Window.SetWindowPos(hWnd, OpenNETCF.Win32.HWND.BOTTOM, 204,
295, 36, 24, SWP.SHOWWINDOW)

thanks,
Michel
 
D

Daniel Moth

VB does not support operator overloading which is the root of your problem
(and the reason it works in C#).

Assuming your compiler error is on the last line, replace the first
parameter (hWnd) with:
Win32Window.op_Implicit(hWnd)
and it should compile.

BTW, VB2005 supports operator overloading so if you try your original VB
code in VS2005 Beta 2 you'll find it works.

Cheers
Daniel
 
G

Guest

Daniel Moth said:
VB does not support operator overloading which is the root of your problem
(and the reason it works in C#).

Ah yes... The VB.Net limitations haunting me again... Too bad there's an
anti "anything that looks like C" culture here.
Assuming your compiler error is on the last line, replace the first
parameter (hWnd) with:
Win32Window.op_Implicit(hWnd)
and it should compile.

That seems to have done the trick - thanks!
BTW, VB2005 supports operator overloading so if you try your original VB
code in VS2005 Beta 2 you'll find it works.

I haven't installed that yet. We're soon going into production so
unfortunately I haven't had a chance to check out the new goodies...

thanks,
Michel
 
T

Thomas Hall

Hello Peter,

I uninstalled v1.3 from Add/Remove Progs before I installed v1.4 but
noticed several OpenNETCF assemblies that were left in the
..\CompactFrameworkSDK\v1.0.5000\Windows CE folder. Should these be
manually deleted before installing v1.4 or will updated assemblies be
overwritten? Also, I installed the Library content and noticed alot of
"Summary missing" errors in the docs.

Just curious,
Thomas Hall
 
P

Paul G. Tobey [eMVP]

Yes, you can manually delete anything with "opennetcf" in the name from the
VS.NET folder. It probably won't hurt to leave them, either. The 1.4
uninstaller fixes this...

Paul T.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top