×

First time here?

You are looking at the most recent posts. You may also want to check out older archives. Please leave a comment, ask a question and consider subscribing to the latest posts via RSS or email. Thank you for visiting!

Q: Why do I get “Request for the permission of type System.Security.Permission.FileIOPermission“?
Q: I am getting an error immediately after I add your web part, what's the problem?
Q: It says your web part is not marked as safe? What does that mean?
Q: I ran your install .msi file but the web part does not show up in the Virual Gallery, what happened?

A: Per the readme file, there are two methods of installing FeedReader.  The first method is to change the trust level for the portal from WSS_Minimal (which is out of the box configuration) to Full.  The second (and recommended) method is to ensure the web part is installed into the GAC.  This is accomplished using:

stsadm.exe -o addwppack -filename -globalinstall -force

You'll notice the “-globalinstall” parameter which installs FeedReader to the GAC for you.  This should solve the problem described above.

The other option instead of the “-globalinstall“ option (which puts the Web Part in the Global Assembly Cache) is to edit the web.config of the SharePoint server.  You will notice in the web.config a section that indicates a trust level.  By default this will most likely be something like “WSS_Minimal“ unless it has been changed.  You can change this to “Full“ and FeedReader should work.

Q: My company uses a proxy server which requires user authentication, does FeedReader work?
A: We are trying to do our best to accommodate all environments, and proxy servers are one that are a pain point for us right now.  Because the server is actually making the request for the RSS feed information, we are challenged with making sure all the credentials are appropriately passed on through FeedReader.  Updates on this issue will be continually posted here.

References: http://msmvps.com/cgross/archive/2004/06/26/9045.aspx



DISCLAIMER:

The opinions/content expressed on this blog are provided "ASIS" with no warranties and are my own personal opinions/content (unless otherwise noted) and do not represent my employer's view in any way.