If you haven’t agreed to the iPhone SDK License Agreement and NDA, please ignore this post, or Apple might hunt you down with their lawyers… and what a horrible death that would be.

Problem

I keep getting a build error when trying to subclass the UITableViewCell

Solution

Add the CoreGraphics.framework to your project

Resource

Found my answer at the MacRumors forums.

Related posts:

1. ASP .NET & System.Threading.ThreadAbortException Error
2. iPhone SDK DNA – A Frustrating Issue
3. iPhone SDK – Learning the Basics by Removing the Touch

Later I discovered that an extra space was being added before the Doc-Type was inserted, so it was invalidating our Doc-Type and threw off the parsing of our page on several browsers. After hours of research and debugging I found out a class file that we were loading via autoloading was leaking a space to the output. I couldn’t figure out where, or how. I read and re-read the code 4-5 times before I decided to give up. I couldn’t figure out where the extra space was coming from.

So I decided to “buffer protect” all my code in my autoload. Basically, I did something like this:

function __autoload($class_name)
{
   // Start an output buffer to catch all text sent to browser
   ob_start();
   // Load the file
   require_once($class_name.".php");
   // Get the contents and save them to no variable. If you wanted to see what was sent to the output
   // you can get it by doing $var = ob_get_contents();
   ob_get_contents();
   // Stop the output buffer and clear its content.
   ob_end_clean();
}

That would ensure that if a class on accidently send text to the output, this would protect against it. I hope this helps someone.

Related posts:

1. PHP5.x or PHP6 – Argument for Type-Hinting: Better IDEs

Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack.

I was really confused because everything seemed to be working just fine, then I found this forum thread. Turns out there are several causes for this error, but mine was caused by doing a Response.Redirect(); from within a Try-Catch statement. Apparently ASP .NET does not like that.

Workaround

In a try-catch statement, use a boolean variable to mark weather or not to Redirect (or some other variable to accomplish your logic) and preform the Response.Redirect(); outside of your Try Catch. On a side note, I’ve successfully been able to Redirect from inside the Catch {} aspect, just not the try {}.

Resources

Here is the link to the forums that I found my answer:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=268544&SiteID=1

Related posts:

1. ASP .NET 2.0, GridViews, HyperLinkField, and JavaScript