Thursday, November 5, 2015

iText / iTextSharp Presentation for MSDevWNY User Ggroup

On November 10th 2015 I presented on iTextSharp for the MSDevWNY User Group.

The meeting was held at Campus Linc (25 John Glenn Drive #102, Amherst NY)

I presented a demo Web Forms application I created.  I showed how to create PDF files entirely in code.  I will also show how to take an existing PDF Form and fill it out using the C# version of the Java iText library known as iTextSharp.  I also show how to generate PDF's from within an MVC Application.

The original meetup post is available here.

I have also created a custom iText / iText Sharp Point Ruler to help you when taking measurements for a document you are creating with iText. If you were in attendance at the meeting you would have received one.

 If you were unable to attend you can still download and print your own Point Ruler. This ruler is designed to be printed on 12" x 18" cardstock paper. When printing be sure Adobe Reader is set to print in actual size without scaling (Otherwise the ruler will not be accurate). If you are unable to print on paper that large simply print the ruler on as big a sheet of paper as you can.

I am including a Single ruler version as well as a version that allows you to print 5 rulers at a time.

iText / iText Sharp Point Ruler Single Print
iText / iText Sharp Point Ruler Multiple Print

Here are links to my PowerPoint slides and sample application:

iText / iTextSharp PowerPoint Presentation
iTextSharp Demo Application VS 2015 Solution

If you have any questions or comments about my presentation please feel free to leave me a comment below.

Wednesday, August 14, 2013

Problem resolving some host names such as on Windows Server 2008 R2

For some time we have been receiving a "This page can't be displayed" error when going to certain parts of the Verizon Wireless website.  Turns out it was an issue resolving the hostname  The issue would only occur from machines running internally on our network that point to a Windows Server 2008 R2 DNS server. 

After much digging it turns out that Verizon has some issues with the ttl values for their CNAME records.  Basically the CNAMES are cached longer than the A records they point to.

This became an issue with DNS because Microsoft made some security changes in Windows Server 2008 R2 Microsoft to prevent DNS Poisoning. You will only notice this issue if you use Root Hints instead of forwarders.

You can read more about the issue here.

Microsoft has issued a hot fix to resolve this issue and you can find that here.

The hotfix will require a server restart in order to fix the issue.