Compilation errors when changing from SDF 1.4 to 2.0 Beta1

[Lonifasiko]

I downloaded and install SDF 2.0 Beta1 a few days ago.

In order to test new functionality, I removed all references to SDF 1.4
and added new references to SDF 2.0 libraries. I thougth the
compilation was going to have success, but it didn't

The most strange was that SDF 2.0 did not recognize classes such as
RegistryKey class under Win32 namespace. And I cannot find RegistryKey
class anywhere in the new library!

I thought SDF 2.0 would cover (with little naming changes) all
functionality inside SDF 1.4. Is this correct?

These compilation errors could be because SDF 2.0 is still in Beta?

Thanks for all your effort OpenNETCF team!


Regards.

 

[Daniel Moth]

RegistryKey is now part of CF v2.0. So replace your references from
OpenNETCF.Win32 to Microsoft.Win32.

If you have any other compilation errors do let us know.

Cheers
Daniel

 

[Chris Tacke [MVP]]

SDF 2.0 is *not* binary or interface compatible with SDF 1.x, so compilation
errors are to be expected. A large amount of stuff was picked up by CF 2.0,
so we dropped support for those items. We also refactored several things
that we felt needed improvement. There should be no loss of capabilities,
but occasionally it might be a challenge to find where the function went.
Feel free to post back if you have trouble finding other items.

-Chris

 

[Lonifasiko]

Thanks guys,

What fool I'm that I've not searched RegistryKey under CF 2.0!

I think I'll add references to SDF 2.0 again in my project! I think
that was the main compilation error I was having!

I'll tell you if anything else goes wrong!

Thanks again very much.

 

[Hilton]

What if the user isn't running CF 2.0? I assume then that SDF 2.0 is only
intended for 2.0 devices which means that it has limited usefulness (for
me). It sure would be nice if all developers could force their users to
install CF 2.0.

Hilton

 

[Lonifasiko]

Hi,

Good news! I compiled again my project using SDF 2.0. Here is my
feedback:

I've had problems when compiling with
"OpenNETCF.Multimedia.Audio.Player" class, that seems to have been
renamed to "OpenNETCF.Media.SoundPlayer".
System.Windows.Forms.ButtonEx hs also be renamed to Button2, and now
AutoSize property have been removed from the control.
OpenNETCF.Drawing.ContentAlignment2 enumeration offers now more options
than the old OpenNETCF.Drawing.ContentAlignment.

These have been all my troubles when compiling using SDF 2.0 ;-)

What about SoundPlayer class supporting MP3 playing? In the
documentation it only says that play .wav files. Have you planned
supporting MP3 or should I continue using FMODCE library?

Thanks very much.
Thanks very much.

 

[Chris Tacke [MVP]]

The source will be available when we release, so you can always recompile it
under CF 1.0. It's just not a scenario we're putting effort into
supporting.

-Chris

 

[Daniel Moth]

SDF v2.0 is for VS2005 and CF v2.0. So, like CF v2.0, it is applicable on CE
5.0, WM2003 PPC and WM5.

If you are still working with CF v1.0 then please continue to use SDF v1.4
which remains freely available. Even if you get the source for SDF v2.0,
some features will rely on CF v2.0 functionality so it will be more effort
than is worth to port it against CF v1.0

Cheers
Daniel

 

[Lonifasiko]

Hi Chris,

Perhaps you've misunderstood me. I was not asking you for the source
code. Are you referring the previous post? I only wanted to share with
the group the few problems I have had when moving to SDF 2.0. I cannot
even say "problems", because have been minimal issues rapidly solved.
Moreover, I expected much more trouble, but it's crystal clear that all
your team's work is incredible!

My post indeed intended to let people know that there is no trouble and
headaches when moving from SDF 1.4 to 2.0, that it's really simple and
easy.

Congratulations for all your work! Well done!

Regards.

 

[Daniel Moth]

Look at the thread... Chris was replying to Hilton...

Thanks for finding it straightforward to recompile against SDF v2.0. We will
provide an upgrade guide so it is even simpler.. keep an eye on the
opennetcf blog and keep reporting any issues here.

Cheers
Daniel