Compact Framework 2.0 team needs to finish the .NET CF 2.0 release

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In my latest blog

[http://realworldsa.dotnetdevelopers...0_team_needs_to_finish_the_net_cf_20_rele.htm]

I list several links to CF 2.0 shortcomings.

It is evident that the CF 2.0 team needs to be pulled out of whatever they
are working on in WCF and come back to finish the .NET CF 2.0 release.

I keep hearing "We are listening", but I think we've said enough that it is
now time to start producing. The Compact Framework 2.0 team needs to finish
the .NET CF 2.0 release.
 
The Compact Framework 2.0 team needs to finish
the .NET CF 2.0 release.
Click to expand...

What?

I bet you'll see a Service Pack for it. Nothing is ever perfect and Rome
wasn't built in a day.

I'm sure they also would appreciate your observations if presented. Try not
to be a confrontation in the future and you'll probably end up a valued
member of the community. Your complaints on your blog are irrational and
over expectant. One of them seems to be, "I didn't get the code sample I
needed".

Why don't you ask for help instead of being pissed about not getting what
you "expected"? That would be a good start. You can communicate from there.
 
It did start with nice enquiries a little over a month ago and the only
responses I got were "Look at OpenNETCF", "Sorry we have moved on to WCF",
"We didn't have the time", "Put it in the product suggestion site", or "We
wanted to but didn't get to it". My nice enquiries didn't get me or the
other people I know who are looking for the same thing anything. So I am
trying a different route. I don't feel as if the release was given the
attention it needed because Microsoft is moving so quickly towards their next
release. I am sure it is not the teams fault, but the people coming up with
the timelines that forced them to take shortcuts should be made aware they
made a bad business decision, and released an unfinished product.
 
Documentation should be produced, and they are still releasing white papers
regularly on CF 2.0 (yes, they should speed up) ans I'm sure your requests
for topics have been heard.

However you can be assumred that it's unlikely that new features will be
added in a SP. MS is trying to not do that, as it causes breaks. So cals
for WSE3 will likely never be fulfiled. If you need it, you're going to
have to roll it (or a substitute) yourself.

-Chris
 
Please, in all fairness ....

I think that anyone using the .NET CF 2.0 for enterprise development do
agree that the VS2005 release is "not the best".

It is not "irrational and over expectant" to expect an IDE that:
- have a conversion wizard that, well, actually convert to 2.0 format
- have a debugger that, well, actually do debug(on a regular basis, with
symbols consistenly loaded to device)
- have the display of forms that, well, is not corrupted at irregular
intervals
- have a "time of display" for forms that, well, of even medium sized
forms does not take like ages
- have an IDE that, well, at best may be described as "sluggish"
- .....

Any, (and I mean any), links or suggestion to service packs or quick fixes
for IDE that may cure these or other bugs for CF development is more than
welcome.

Regards, Swan B.
 
Excellent summary on a lot of things that my "irrational and over expectant"
don't even touch on.

On more thing to those that are defending the team... THEY ARE THE ONLY
TEAM THAT HAS COMMENTS DISABLED ON ALL THEIR BLOGS. They all are responding
with submit it to the suggestion site. In other words, "We aren't interested
and are working on something else".

The bottom line is they aren't done doing their job, and they need to finish
it.
 
Ted,

There is a few reasonsthey refer you to suggestion site - any submition goes
directly to a database, that's being used from an internal application and is
available for "decision maker" level people in the team.
 
Thanks Alen,

I have pretty much come to the conclusion that nothing will be done, and we
are stuck with what we got.

Tad
 
Ginny, thanks for your comment.

My development computer(hopefully reasonable satisfactory stats ?)
1 GB RAM, 2,4Ghz Pentium Mobile, Disk 7200 rpm

To focus the thread:
We do agree that the documentation and communication etc. could have been
better, but have any seen any statements from MS for cleaning up the
"quirks" in the IDE that effectively stops us from doing our job ?

We are kind of "stuck in the middle", "too late" to revert the solution back
to VS2003, but development speed in VS2005 is soo sloooow that "it hurts".


Regards, Swan B.
 
Tad said:
Thanks Alen,

I have pretty much come to the conclusion that nothing will be done, and we
are stuck with what we got.

Tad
Click to expand...

Hello,

could you post the URL of this site? Is it a general suggestion site? Is
it like a bug tracking system?

Greetings

Markus
 
Swan,

I agree that your dev machine seems adequate so I'm surprised that you're
finding the performance worse than VS 2003 - my experience has been the
reverse.

Are you debugging on the emulator or on the actual device? I find that for
modern devices, debugging to a USB attached device is faster.

HTH,
 
Always debugging on device.

(that is, we debug when VS2005 allows to do so)

We are haunted by the VS2005 IDE error:
The breakpoint will not currently be hit. No symbols have been loaded for
this document.

First investigations seems that the IDE for some reason are not deploying
the latest .exe and .pdb to device.
Any suggestion to this one is welcome.


Regards, Swan B.
 
By any chance, is that breakpoint in the DLL which is dynamically loaded (or
P/Invoked from managed code)?

VS (and other debuggers) can only set break point if DLL has been loaded
into memory.



If that's not the case, it would complain what breakpoint can't be hit as no
code is loaded at this location (or something like this).

If that's what you see, please try setting up another break point right
after DLL is loaded by your code.

VS would notice code is available and activate break point in the DLL.



PDBs are never deployed to the device. If VS can't find PDBs, please set up
correct search path for symbols in project properties.


--
Best regards,

Ilya

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

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).
 
Thank you very much for quick response.

By any chance, is that breakpoint in the DLL which is dynamically loaded
(or P/Invoked from managed code)?
Click to expand...

No breakpoint code in dynamic DLL in project
PDBs are never deployed to the device.
Click to expand...
That is right :-)

Assume that PDB is
If VS can't find PDBs, please set up correct search path for symbols in
project properties.
Click to expand...

Assume you mean the setup search path in Tools, Option, Debug, Symbols for
the solution
(This is set to obj/debug nad then to bin/debug )


After even further investigation it seems that the newly built .exe is not
copied to the device ?
This is a mystery...


Regards Swan B.
 
So, break point is in EXE, is that right? Is that managed or native EXE?

Could you please post deployment log?


--
Best regards,

Ilya

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

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).
 
Hi
I got a similar system and I also experience performance problems.

In some action I got to wait about three seconds till the IDE is
responsible again.

But when I see all the new possibilites I feel quite good with VS2005
even if there plenty of small bugs (like elements changing position in
Designer by it self etc...)

I hope that there will be an SP and thing are going a little better.
 
Back
Top