ANN: .NETCF v1.0 Service Pack 3 Now Available

  • Thread starter Thread starter Peter Foot [MVP]
  • Start date Start date
P

Peter Foot [MVP]

The .NETCF v1.0 SP3 Redistributable package can be downloaded from here:-

http://www.microsoft.com/downloads/...11-194b-4c00-b445-f92bec03032f&displaylang=en

List of fixes grabbed from the above page:-

Fixed Issues:
- Transitions between managed and native code can cause memory leaks on ARM
platforms.
- A NullReferenceException is thrown when a Web Method returns an empty
array using the xsi:Nil attribute.
- Modifying the SoapClientMessage.ContentType property does not modify the
Http requests ContentType header.
- Stack corruption can occur on SH, MIPS and x86 platforms when local
variables are created but never used.
- Invoking a multicase delegate from a catch handler throws a
MissingMethodException on SH, MIPS and x86 platforms.
- Command line arguments containing double byte characters are truncated to
a single byte.
- An ObjectDisposedException is thrown when a asynchronous web request is
aborted before the response is received.
- Invoke on a disposed control hangs the application.
- Any array containing one or more elements is not sent to the Web Service
correctly.
- An application may hang when invoking a Web Method that uses multiple
XmlElementAttributes on a single argument, member or property.
- Memory corruption can occur on devices that have the native security model
enabled and both .NET CF V1 SP3 and a pre-release version of .NET CF V2
installed.
- Deadlocks can occur when running under severe resource constraints.
- Tool Bar's on Windows Mobile 2003 SE no longer lose their images when
removed from the form.
- An uncatchable ObjectDisposedException is thrown when the server closes
the socket connection.
- Setting the Minimum and Maximum properties of a progressbar no longer
crashes the application.
- Unexpected exception while adding an image to an imagelist on an Hx4700
and hx4705.
- Data Misalignment occurs on Decimal fields in MIPSIV devices.


(http://blog.opennetcf.org/pfoot/PermaLink.aspx?guid=f874a16c-7541-46f0-aa9d-babeab48f0b6)

Peter
 
You beat me by a minute :-D

It seems to be the same as the QFE that was released in November

Cheers
Daniel
 
No. Actually this one was even better. IIRC the QFE was *post-SP3*, i.e. it
addressed an issue introduced by SP3.
 
The fix list and build numbers looks the same, probably this is a kind of
SP3 Re-release and the previous build destined to be SP3 (which the QFE
refers to) didn't ever get released.

Peter
 
As we know, every CF release has two parts: MSI and QFE

Given that the build number and fix list are the same, the November QFE *is*
SP3 (unless we get another QFE labelled SP3 which has the same build number,
which would be strange). As for the actual fix list...I have never seen a
fix refer to bugs *it* introduced, so expect a StackOverflow anytime now :-)

In the past we always got the QFE much later hence this is a pleasant
first... for me anyway :-) May I ask for a CF 2.0 Beta QFE please?

Cheers
Daniel
 
Quoting from your November post:

[QFE Fixlist]
k.. Memory corruption may occur on devices that have the native security
model enabled and both .NET CF V1 SP3.

The grammar notwithstanding, in my book it translates as "fixing an issue
that has SP3 as a prerequisite"
 
That is exactly my point too:
"I have never seen a fix refer to bugs *it* introduced, so expect a
StackOverflow anytime now :-)"

....maybe I should add: "until now" :-)

Cheers
Daniel
--
http://www.danielmoth.com/Blog/


Alex Feinman said:
Quoting from your November post:

[QFE Fixlist]
k.. Memory corruption may occur on devices that have the native security
model enabled and both .NET CF V1 SP3.

The grammar notwithstanding, in my book it translates as "fixing an issue
that has SP3 as a prerequisite"


--
Alex Feinman
---
Visit http://www.opennetcf.org
Daniel Moth said:
As we know, every CF release has two parts: MSI and QFE

Given that the build number and fix list are the same, the November QFE
*is* SP3 (unless we get another QFE labelled SP3 which has the same build
number, which would be strange). As for the actual fix list...I have
never seen a fix refer to bugs *it* introduced, so expect a StackOverflow
anytime now :-)

In the past we always got the QFE much later hence this is a pleasant
first... for me anyway :-) May I ask for a CF 2.0 Beta QFE please?

Cheers
Daniel
Click to expand...
Click to expand...
 
We had a couple of SP3 release candidates, could the QFE you're talking
about have been RC1? I don't remember issuing a QFE in November (...I sit
in the office next to the builder and across from the release manager!)

Cheers,

Ryan Chapman
.NET Compact Framework

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Ahhh, Thanks Daniel!

That's our SP3--I was unaware that CE got the release out ahead of us!

Cheers,

Ryan

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top