One of my applications streams PDF files (or any other type the user hapens to upload as an attachment).  Prior to the Adobe reader 9.4.2 update, the browser never had an issue
displaying the file.  After the update, the browser would no longer display the file, it would only allow the user to save the file to their hard drive and then open it up.  The dialog
that was displayed to the user had an interesting message at the bottom:

"The file you are downloading cannot be opened by the default program.  It is either corrupt or it has an incorrect file type.  As a security precaution it is recommended that you
cancel the download."

I finally found a post on the Adobe forums today that has many different solutions from many different developers that have worked around the issue, and I was also able to resolve
the issue for my application by using bits and pieces of the solutions provided in the forum post (http://forums.adobe.com/thread/391712).

Here was my code prior to the workaround:

    Dim DR As SqlDataReader = SqlHelper.ExecuteReader(Utils.HPSConn, CommandType.StoredProcedure, "hold_ticket_item_attachment_view_by_id", New SqlParameter("@id", Attachment_ID))
    If DR.Read Then
     Response.ClearContent()
     Response.ContentType = DR("mime_type").ToString
     'inline:  opens document in same browser window so that we do not have orphaned browser when done.
     'attachment:  opens in a seperate window, so we have an orphaned browser when done.
     Response.AppendHeader("Content-Disposition", "inline; filename=""" & DR("file_name").ToString & """")
     Dim file_data As Byte() = DR("file_data")
     Response.BinaryWrite(file_data)
    End If
    DR.Close()
    DR = Nothing

Here is the code that is now functioning as it should:

    Dim DR As SqlDataReader = SqlHelper.ExecuteReader(Utils.HPSConn, CommandType.StoredProcedure, "hold_ticket_item_attachment_view_by_id", New SqlParameter("@id", Attachment_ID))
                If DR.Read Then
                    Response.ClearHeaders()
                    Response.ClearContent()
                    'Content-Disposition:
                    'inline:  opens document in same browser window so that we do not have orphaned browser when done.
                    'attachment:  opens in a seperate window, so we have an orphaned browser when done.
                    Response.ContentType = DR("mime_type").ToString
                    Response.AppendHeader("Content-Disposition", "inline;filename=""" & DR("file_name").ToString & """")
                    Dim file_data As Byte() = DR("file_data")
                    Response.BinaryWrite(file_data)
                    Response.End()
            End If
                DR.Close()
                DR = Nothing

You'll notice the only 2 changes I made were to add the lines in bold.

Seems the changes (in Adobe Reader or the browser or whatever changed to cause this behavior) are "fixed" by making sure the response stream is clean and is properly terminated.

If you read yesterday’s post, you know I was having a hard time with a report that uses an AspxGrid to display the data.  I solved the problem that was causing an error when I did a postback and the number of columns had changed, but then I started working on adding totals to the footer and ran into another issue.

I couldn’t figure out for the life of me why I could specify a column by name and add the total, but when I tried to determine the column names (since they are dynamically generated) so that I could add the totals (that is how you do it with the DevExpress AspxGrid), the footer was always blank.

I finally figured out the issue was a timing issue.  If I try to set the totals up after databind, they do not show up because that is when the control actually calculates the totals.  I couldn’t figure out how to get the names without databinding either, so I thought I was stuck.  Then, the light bulb flickered.  I decided to just look at my datatable (since it has the field names I am using in it) before I do the data bind and setup the totals.

DevExpress has some good examples of how to set up the totals in the footer, just none that help you figure out the column names when you don’t know them.

I am participating in the Dallas GiveCamp next weekend (1/14 – 1/16) and attended the orientation meeting last night.  At the meeting we heard information about what happens during the weekend and what will be expected as well as information about all of the charities that are part of the event.

I have been interested in volunteering for a couple of years, but the weekend was always a bad one for me.  I am glad this year the weekend is one where I do not have any prior commitments.  However, I was a bit unsure of the whole 1 weekend to develop a working application aspect of the event, but after the meeting last night I am excited to be a part of it and feel the team I am on will be able to do some great things.

If you are in the Dallas area and have free time over the weekend of 1/14, please go sign up.  I am sure they will still accept volunteers.

I’ll post at least one update after the event to let everyone know how it went.

www.dallasgivecamp.org

For anyone else who uses DevExpress AspGrid control, this may help you get past an issue if you are dynamically generating the columns and there is a possibility your number of columns will change with each postback.

I wasted about 30 minutes today trying to figure out why I was receiving errors the second time I ran a report (with different criteria).  One of my co-workers found this link:

http://www.facebook.com/note.php?note_id=192123579523

Two things I took away from this:

1)      I didn’t know DevExpress had a facebook page that actually had useful information on it.

2)      I love DevExpress products, but I sometimes don’t like the little quirks that come along with them.

Saw a blog post today that mentioned this excellent cheat sheet for string formatting options.  A definite must have piece of cubicle art.

 http://www.quicklycode.com/cheatsheets/net-string-formats-cheat-sheet

I had an issue today where an outer apply on a table valued function kept giving me strange errors.  After wasting about 30 minutes trying to figure out what I had done wrong, I Googled it and found a few small passing references to the database setting (under properties - options) for compatability mode.  Sure enough, when I looked at the setting, it was set for SQL Server 2000 (80) and this is a 2005 database.  When the DBA upgraded our databases from 2000 to 2005, he "forgot" to change this.  I had him make the change and now the outer apply with a table function now works. 

This one is too good not to keep track of....

Rick Strahl always comes up with great stuff, and this is definitely an excellent implementation of a pager control:

 http://west-wind.com/weblog/posts/114621.aspx

I have been banging my head on the desk with an issue for the past couple of days.  Thanks to Dan Maharry's blog, I have finally solved the issue.

http://blog.hmobius.com/post/2009/08/07/Debugging-ViewState-Errors-Visual-Studio-Debugging-Options.aspx

(Just wanted to keep this here for future reference)

Ran into this issue when promoting an upgrade from dev to staging today.

The site was upgraded from 2.0 to 3.5.  I searched all over and found a lot of answers, but the final fix was to add 2 0 (zero) byte files in the root of the website:  ScriptResource.axd and WebResource.axd.

Go Figure....

I assume if I were to create a brand new project in VS 2008 it would add these 2 files and the upgrade process does not.

Oh well.  At leaset my web server admin had written down a note when someone else ran into the same issue.

Just began working with VS 2008 and finally, MS got the version number auto increment right with this release.

Now, if you specify the following in your assemblyinfo.XX file:

<Assembly: AssemblyVersion("1.0.*")>

You'll get a true auto increment based on date/time.

 Build number is the number of days since Dec 31, 1999 and Revision number is the number of seconds since midnight, divided by 2.

Something like this:

1.0.3362.13952

If you want more control over it, there is also a nice little add-in out on codeplex that allows you to control it better: http://autobuildversion.codeplex.com/

 Also, if you want the AssemblyFileVersion to be the same as the AssemblyVersion, just comment it out or remove it from the assemblyinfo.XX file.