The sample code on page http://msdn.microsoft.com/en-us/library/ff967559(v=VS.92).aspx where the page is titled How to: Implement the Trial Experience in Your Application for Windows Phone - the sample code is shown as using Microsoft.Phone.Tasks;
public MarketplaceDetailTask detailTask = new MarketplaceDetailTask();
private void buy_now_Click(object sender, RoutedEventArgs e){
detailTask.Show();
}

leads a new developer to misinterpret this as the exact code that should be in the click event, which isn't the case. Please use greyed-out, ellipsed text (or something like that) to indicate that text is missing and what the text is for and what it does.

All three snippets of sample code should work together in terms of names and purposes, which they currently don't.

At the moment (and particularly with the initial release of WP7 o/s and handsets) - there's a number of known 'bugs' in the platform - which is of course expected, understandable and 'forgivable' given it's a 1.0 release.

Unfortunately - developers quite often get blamed for these problems by end users (and in worst case are given a bad reviews such as '1 star') - as there is no education or information available to end users about any of these problems.

The big problem however is that Microsoft are simply not admitting to any of these problems - so developers are left to try and 'convince' users it wasn't their app (or that there's nothing they can do about issue).

A very common/classic example is the marketplace app bug in pre nodo updated devices where trial versions of apps could not be updated (unless user uninstalled app completely and reinstalled new version).

In case of abovementioned issue - the new Microsoft update information site simply referred to these marketplace bug fixes (for updating trial apps) as 'enhancements to marketplace app' (with no mention of the actual bugs being fixed).

This seems to be a very different way of dealing with bugs and fixes than in the past (ie. Windows/.NET/SQL Server/Silverlight developers are all used to frank and open admissions of bugs) - and Microsoft used to publish knowledgebase articles that could be referred to the users in these cases.

As a developer I'd have nothing but respect for Microsoft WP7 team if they were open about these bugs and fixes being done. At least we'd know they were being addressed - and similarly we could give our app customers the comfort of knowing that their problems will be fixed in future.

Can we have better quality documentation on MSDN? (Especially context help from Visual Studio)? I am coming from Win32 background, and I am used to having very detailed better documentation. In WP7 world, I have below problems
1. The default context passed from Visual Studio. When I have a WP7 project open why can't the context documentation default to Silverlight? Every time it opens in "NET Framework 4" context, and I need to change to Silverlight to get WP7 specific version
2. Utter lack of documentation of few controls. E.g. Pivot Item SelectionChanged event
http://msdn.microsoft.com/query/dev10.query?appId=Dev10IDEF1&l=EN-US&k=k(MICROSOFT.PHONE.CONTROLS.PIVOT.SELECTIONCHANGED);
Only valuable line in that whole page is “Occurs when the currently selected item changes.”. It does not even link to SelectionChangedEventArgs, what is the type of Sender? How do I get the selected PivotItem? How to PivotItem that lost selection?