Hello, great example. I can't found the AdvViewer section. Where can I found it?

Hi Euclidez,

 We've removed the AdViewer project from this release, it's something we may add back in for a future release. You can work around this by creating a simple test feed with your ads in it and view it in the SceSampleReader built to Release mode (Debug mode actually disables ad display).

Thanks,

Chris

Is the MSDN Reader supposed to show the actual article content?  Whenever I click on an article, it switches to what looks like should be the article screen, but never shows an article.  It stays blank and says Page 0/0.

This would be really cool if it was fleshed out a little more.  (More connection information showing what is going on, alerts, etc)

Hi Stritch,

 Thanks so much Stritch for reporting this. Our apologies, we just found the bug that is causing this. Our SubscriptionSync library is not handling some web server's http compression properly. We have the fix ready and are going to package it up for both the SCE Reader Source Code and get the MSDN app updated (along with source code). You can expect this to be up early next week. We'll post back here when it's available.

Thanks again,

Chris

Stritch and others,

 We have fixed the MSDN application and made the corresponding fix to the SCE Reader Source code for the above issue. Additionally, we've posted the entire source code for the MSDN Reader (available here: windowsclient.net/.../MsdnReaderSourceCode.exe). We hope that it'll serve as a useful sample in building your own custom SCE application.

Please do let us know if you run into any issues or have any questions regarding the kit.

Thanks,

Chris Han

Hi.

I downloaded the sce Starter kit but I can't found in this distribution the following projects:

- Reader Quick Start wizard

- Photos: a simple sample demonstrating a syndicated photo experience (full sample source code)

- An integrated branded boostrapper for .Net 3.0 deployment and app installation via Click-Once

- Content Sync Extensions for RSS 2.0 for rich, nested, authenticated feeds

windowsclient.net/.../sce-get-more-details.aspx

Where I can found it?

Chris:

Although the app (MSDN reader) updated itself today, I still don't see any content beyond the section pages.  Is there something else we are supposed to do?  Thanks.

Still can't find the Photo Viewer app or source code. And the MSDN reader, while pretty darn cool, doesn't supply article content for many articles, just blank pages.

Also, there are some namespace declaration issues in the SceReader sourcecode. It could build and run but wouldn't allow the designer for the main page.xaml  to load properly until these were fixed in several of the various *resources.xaml files. Declarations were fixed by changing "namespace:SceReader" to "namespace:Microsoft.SceReader" .

Raised error in designer with blue squiggly:

xmlns:SceReader="clr-namespace:SceReader;assembly=SceReader"

No Error in designer:

xmlns:SceReader="clr-namespace:Microsoft.SceReader;assembly=SceReader"

Hi Malshep,

 Thank you for alerting us to this problem. Unfortunately the feed update date hasn't changed so you're still viewing the old data. Below are instructions on how to clean your cache and fix this issue. We're also trying to get the feed update date changed to fix this problem as well. But the below instructions should make it work instantly. Please let us know if you run into any issues after following them:

###INSTRUCTIONS FOR HOW TO CLEAN YOUR CACHE###

1. Close MSDN Reader

2.

On Vista:

Navigate to this directory: C:\Users\**Your user name here**\AppData\Local\MSDN Reader\MsdnReader\

and delete the 'Cache' folder.

On XP or Server2003:

Go to C;\Documents and Settings\**Your user name here**\Local Settings\Application Data\MSDN Reader\MsdnReader\

and delete the 'Cache' folder.

3. Restart the MSDN application, it should begin syncing and you should see the actual data.

Again, please let me know if you still run into problems.

Thanks for your patience!

Chris Han

Gringotuc and Beitz,

Apologies for our mistake here. The quickstart wizard and the photoviewer application are upcoming additions to the SCE starter kit and are not yet released.

However, the

"integrated branded boostrapper for .Net 3.0 deployment and app installation via Click-Once"

and "Content Sync Extensions for RSS 2.0 for rich, nested, authenticated feeds" are actually there. The boostrapper is in the Setup directory of the SCE Reader source code and you can read more about how to use it here:

windowsclient.net/.../sce-clickonce-msi-hybrid-setup.aspx.

The CSE extensions spec is located here: windowsclient.net/.../sce-content-sync-ext.aspx. And the SceReader.dll with reference source code does utilize these CSE extensions.

Beitz, thanks so much for finding the namespace naming bug! We added the 'Microsoft.' prefix within the last few weeks before shipping so we must have neglected to change it within that page. I will file a bug in our internal database to ensure that we fix it in our next drop. Apologies about the mistake.

Please see my post with instructions on how to clean your cache to alleviate the problem with the MSDN Reader.

Thanks again for the feedback and prompt notification of the issues you're running into. We very much appreciate it.

Chris:

Thanks.  Seems to be working.  Very cool!

Malshep and others who noticed the article data was absent in MSDN - thanks for pointing this out to us. We actually did change the feed update dates, but because of the way ClickOnce updates are applied, this doesn't help the problem if you already have the old version of the application. The update is only applied on the *first* launch *after* it is downloaded, but by this time the new feed has already been downloaded by the bad app.

We're going to try and rev the feed a couple more times to address this, but cleaning your cache will immediately fix the problem, following the steps Chris described above.

Beitz,

Thanks for pointing out the namespace errors in XAML files. Is it possible to give us some of the file names where you encounted the namespace delcaration:

xmlns:SceReader="clr-namespace:SceReader;assembly=SceReader"

With such a declaration it shouldn't build at all - assuming those resources are being used - so I'm worried that we may have some stale code in there, and I'm having trouble finding it. If you have the file names that would really help, we'd like to fix the problem ASAP.

Thanks again for your prompt feedback, we really appreciate it.

Arathi

Arathi,

IIRC, line 6 in  NavPanelResources.xam was the culprit. I thought it was in more but looking at it now, that's the only one I can find.

Looks like ArrowButtonResources.xaml also has the same "namespace:SceReader" issue.

I've got two SceReader reference assemblies showing up under References in the Solution Explorer. It seems to be the source of a bunch of problems.

After initially being able to load the MainPage.xaml designer, I've been unable to successfully open theMainPage designer due to a series of whack-a-mole errors popping up no matter what declaration names are used (Microsoft.SceReader versus just SceReader, each causes different errors to arise, which keep the designer from opening but don't prevent Building and Running): XAML files fail to load (most often AnnotationResources.xaml); referenced component SceReader and/or SceReaderDesignData can't be found,etc. ...

Installed from scratch and still face the same problems. This is all way beyond my pay grade to figure out. Any guidance would be appreciated. At the end of the day I simply cannot access the designer.

The program builds and runs apparently well. The only issue I notice is that clicking on reading list items either in the docked list or on the Reading List page does not open the article.( But I could almost swear that it worked on my first trials.)

PS - In spite of the frustration, let me thank you for releasing this. This is very helpful and all your work is appreciated.

Take care

Beitz,

I'm sorry about the problems you are experiencing. Looks like we definitely have a way to go in improving workflow with the designer (out of curiosity, are you using Blend or the VS designer?) I will try to figure out what the problem is and have an update or some advice for you shortly. In the meantime - if you're trying to style a specific piece of UI or a resource, maybe I can provide some guidance about how to edit the resource files to produce the change that you need, or how you could plug in a resource/style that you created separately in the designer? Would this help to unblock you?

We'll try to fix this issue as soon as possible, thank you for your patience.

Arathi

Thanks for the help, Arathi. It's appreciated.

I initially started with VS and then attempted to open the MainPage.xaml in Blend 2 to no success. But I went back to Blend 2(September Preview) to give it another shot folliwng yet another install of SceReader (with namespace declarations fixed) and now the MainPage.xaml is opening in the designer. (Wish I had a clue as to why it's now able to open in Blend but not in VS). That's really all I needed at this point as I'm just taking this thing apart and studying your team's work piece by piece. This should be just fiine for my needs right now.

Curious to know if others are having similar issues opening the xaml files in the VS designer, and,if so, how they are resolving them so that I can avoid similiar problems in the future.

Will let you know if any more issues arise. Thanks again for the help. All the best to you and your team and much thanks for putting this together.

The new Seattle PI reader is live now at seattlepi.nwsource.com/newsreader   Give it a try.

Some non-trivial work went into the navigation and input scheme for the Syndicated Client Reader application.  The application supports a full set of keyboard shortcuts as well as Tablet flick gestures such that you can drive navigation with a few keys, your 5-button mouse, a finger or stylus on a touch screen or a remote control.  

The full list is here:

download.microsoft.com/.../SceReader_Keyboard_Shortcuts.docx

Hi,

I am benind a firewall and when I tried to install MSDNReader, it just disapprears when it is trying to synch the application. I see the following error. I have installed it at a home machine and it seems to be working fine. Could this application work behind the firewall?

_______________________________________________________

PLATFORM VERSION INFO

Windows : 5.1.2600.131072 (Win32NT)

Common Language Runtime : 2.0.50727.832

System.Deployment.dll : 2.0.50727.832 (QFE.050727-8300)

mscorwks.dll : 2.0.50727.832 (QFE.050727-8300)

dfdll.dll : 2.0.50727.42 (RTM.050727-4200)

dfshim.dll : 2.0.50727.42 (RTM.050727-4200)

SOURCES

Deployment url : www.windowsclient.net/.../MsdnReader.application

ERROR SUMMARY

Below is a summary of the errors, details of these errors are listed later in the log.

* Activation of www.windowsclient.net/.../MsdnReader.application resulted in exception. Following failure messages were detected:

+ Downloading www.windowsclient.net/.../MsdnReader.application did not succeed.

+ The remote server returned an error: (407) Proxy Authentication Required.

COMPONENT STORE TRANSACTION FAILURE SUMMARY

No transaction error was detected.

WARNINGS

There were no warnings during this operation.

OPERATION PROGRESS STATUS

* [06/02/2008 10:26:50 AM] : Activation of www.windowsclient.net/.../MsdnReader.application has started.

ERROR DETAILS

Following errors were detected during this operation.

* [06/02/2008 10:26:51 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)

- Downloading www.windowsclient.net/.../MsdnReader.application did not succeed.

- Source: System.Deployment

- Stack trace:

at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()

at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)

at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)

at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)

at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)

at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)

at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

--- Inner Exception ---

System.Net.WebException

- The remote server returned an error: (407) Proxy Authentication Required.

- Source: System

- Stack trace:

at System.Net.HttpWebRequest.GetResponse()

at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

COMPONENT STORE TRANSACTION DETAILS

No transaction information is available.

You might want to make sure your anti-virus software is not denying the app access to the internet.

I am able to access other applications fine behind the firewall so that should not be an issue. Unless, there is a port that needs to be open. Is that the case?

Thanks,

Pankaj

Can you check to make sure the reader is on the ALLOW list?  We don't know of any issues with the Reader behind firewalls in general (no special port magic).

Passport sign in does not work on the msdn reader site

code.msdn.microsoft.com/.../View.aspx

I'm not able to sign in to post comments.

Here are my suggestions for MSDN Reader

1. We should be able to save to IE Favorites from MSDN Reader just like from any web page.

2. In the reading list we should be able to create subfolders and store under them

3. The thing I hate about MSDN Reader is that when I click on an article there is no indication if the system is working on my request. There should be a status bar like in IE so we know the system is doing something!

mcp111 - Thank you for your feedback.  I've added your feature requests to our database and we'll consider adding them in one of our future releases.  Thanks!