We recently ran into a situation where a client was unable to use the FDFToolkit.net 2.0 component on a remote server. It worked fine on the testing server.
The error was:
System.Security.SecurityException: That assembly does not allow partially trusted callers
I looked up the error, and found out how to allow the server to trust our component.
SOLUTION:
Since we have the source to our component, as well as the iTextSharp component all we had to do is make some minor changes and recompile.
We opened our sources, and inserted the following line into the AssemblyInfo.vb files for both FDFToolkit.net and iTextSharp:
< Assembly: System.Security.AllowPartiallyTrustedCallers() >
And we made sure the component has the full version information hardcoded in the assemblies.
< Assembly: AssemblyVersion("2.0.0.0") >
Recompiled both components, and the error message dissapeared.
Here's a link to iTextSharp & Partially Trusted web hosts solution:
http://www.jwc3.net/2008/07/itextsharp-will-not-run-in-partially.html
038f7658-5d7b-42b4-af41-29f2d24952cb|0|.0
I recently had a project, using ASP.net 2.0, and manually submitted the site to Yahoo!, MSN, Google. The whole domain placed well on Google, and MSN, but, it seemed we were lacking placement on Yahoo!'s search engine results.
We purchased a paid subscription to Yahoo! Submit express, $50 per domain per year, to diagnose the problem, but we were still lacking hits. I ran a search at Yahoo! for the whole site, it came up with the correct titles, but, the descriptions were not our META descriptions, they were just random text from the content of the pages. I looked at our META information from the HTML page, and the server side META tags were creating an extra parameter, "ID", since it was set to runat="server". I was doing this so I can control the TITLE, DESCRIPTION, and KEYWORDS from within the modules.
Anyway, I fixed the problem, by creating each META tag on the page itself, instead of loading it from the code behind.
The site is now ranking very well on Google, MSN, as well as Yahoo!
Useful links:
64d680e7-8488-495f-9134-ebb0398a48b0|0|.0