.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Post New Web Links

Printing with Windows Forms not properly centered?

Posted By:      Posted Date: November 01, 2010    Points: 0   Category :Windows Application
 
Hi Guys,

I have run into an odd problem trying to do printing with Windows Forms. I needed to add printing to my own code (printing barcode labels), and when I was done my code worked great, except that stuff I had centered on my labels was not actually, well centered! It was always off to the right and down a bit.

So I decided to see what I might have done wrong, and put together a really simple Windows form printing sample program, that would just print something on the page and center it within the page bounds. When I print it on all the printers I have access to here at the office, it does not print correctly. I added code to the print page function to print a rectangle around the margin bounds, which are supposed to be 1" from each corner be default. When it prints out, you can clearly see that the margins are NOT printed in the right locations, yet the item centered on the page is perfectly centered within the margin bounds.

So it would seem I am doing something wrong, but in fact it turns out my code is correct, but something is NOT right with the way Windows Forms handles printing. The reason I say that, is I have since discovered that if I print the document to an Adobe PDF file, or a Microsoft XPS document, when I view the result it is 100% correct! More importantly, when I PRINT that file using Adobe Acrobat, or the Microsoft


View Complete Post


More Related Resource Links

Printing: Preview and Print from Your Windows Forms App with the .NET Printing Namespace

  

Printing is an integral part of every complete Windows-based application. Providing robust printing capabilities in these applications has often proved to be a tedious chore. Now, printing from Windows Forms with the .NET Framework means you must adopt a document-centric approach, resulting in cleaner and more manageable code. While the System.Windows.Forms namespace provides seamless integration with all the standard print dialogs (such as Print Preview, Page Setup, and Print), the System.Drawing.Printing namespace offers numerous classes for extensibility and customization. These classes, and how they provide access to printing capabilities, are covered here. Other useful techniques, such as printing in the background to allow the user to continue other tasks, is also explained.

Alex Calvo

MSDN Magazine February 2003


Application Architecture in Windows Forms 2.0

  
Applications have special support in Windows Forms. For starters, you can manage and tailor your application's lifetime, and, when the work flow is disrupted by an unhandled exception, you can choose from several methods of response. Then, there are several application models that you can employ, including Single Document Interface (SDI) and Multiple Document Interface (MDI) applications, each of which can support either multiple-instance or single-instance mode, the former the VS05 default and the latter requiring special consideration. All applications, however, can discover and use a wide variety of information about the system and environment they execute in.

Application Architecture in Windows Forms 2.0-Single-MDI Applications

  
Consider an MDI application like Microsoft Excel; files opened from the file system (by double-clicking) are all opened as separate child windows within the parent Excel window.7 For the first instance of an MDI application to open a new child window to display the file that was passed to the second instance of the application, the second instance must be able to communicate with the initial instance.

How to programmatically add controls to Windows forms at run time by using Visual C#

  
Create a Windows Forms Application
Start Visual Studio .NET or Visual Studio 2005 or a later version, and create a new Visual C# Windows Application project named WinControls. Form1 is added to the project by default.
Double-click Form1 to create and view the Form1_Load event procedure.
Add private instance variables to the Form1 class to work with common Windows controls. The Form1 class starts as follows:

Bluetooth Printing Guide using Windows Mobile Pocket Pc

  
FieldSoftware Products printing products use the Bluetooth "Serial Port Profile" (SPP). Unfortunately, there is no standard method to find your Bluetooth printer and begin printing... each device contains a Bluetooth stack/driver that determines the steps. There are two main stacks currently available... one from Microsoft and one from WIDCOMM/Broadcom. Below are step-by-step instructions for printing with the Microsoft and WIDCOMM stacks. Note that these may change for different versions of the Bluetooth stacks or for different manufacturers. Consult the documentation for your device for specific details on your device.

Identifying your device''s Bluetooth stack: There is no sure steps to identify a Bluetooth stack on a device. Below are steps for identifying current WIDCOMM and Microsoft stacks at the time this page is published. Note that these may not identify earlier or later versions of the same BT stacks.

How to Localize Windows Forms and Change the Language at Runtime

  
Localization is the process of customizing your application to a particular language, culture or locale. Visual Studio provides support for localizing Windows Forms with much ease. In this article, we will see how to localize windows forms and give the user the ability to change to his preferred language at runtime.
When you run a localized application, the appearance is determined by two culture values. The UICulture property is used to specify which resource files will be loaded for the form. The Culture property, on the other hand, determines how strings such as dates, numerals, and currency amounts are formatted.
Let us see the steps required to create a localized form. You can then expand this example and adopt the same approach for the rest of the forms in your project

Localizing Windows Forms

  
The Visual Studio project system provides considerable support for localizing Windows Forms applications. There are two ways to generate resource files using the Visual Studio development environment: one is to have the project system generate the resource files for localizable UI elements such as text and images on the form. The resource files are then built into satellite assemblies. The second way is to add a resource file template and then edit the template with the XML Designer. A reason for doing the latter is to make localizable strings that appear in dialog boxes and error messages. You must then write code to access these resources.

This walkthrough topic demonstrates both processes in a single Windows Application project.

You can also convert a text file to a resource file; for more information, see Resources in Text File Format and Resource File Generator (Resgen.exe).

http://msdn.microsoft.com/en-us/library/y99d1cd3(VS.71).aspx

CLR Inside Out: Extend Windows Forms Apps Using System.AddIn

  

See how Windows Forms applications can be adapted to use the new .NET Add-in framework (System.AddIn) this month.

Mueez Siddiqui

MSDN Magazine July 2008


GUI Library: Bring the Simplicity of Windows Forms to Native Apps

  

In this article, author John Torjo presents a guide to his C++ GUI library called eGUI++ and explains how it makes user interface programming easier.

John Torjo

MSDN Magazine June 2008


Managed Spy: Deliver The Power Of Spy++ To Windows Forms With Our New Tool

  

Spy++ displays Win32 information such as window classes, styles, and messages. Now you can get that same functionality for managed code using our ManagedSpy. Get it here.

Benjamin Wulfe

MSDN Magazine April 2006


Winning Forms: Practical Tips For Boosting The Performance Of Windows Forms Apps

  

This article discusses techniques you can use to ensure that Windows Forms-based apps provide optimal performance to match the rich UI responsiveness they're known to provide.

Milena Salman

MSDN Magazine March 2006


Text Rendering: Build World-Ready Apps Using Complex Scripts In Windows Forms Controls

  

The System.Windows.Forms.TextRenderer class provides support for complex scripts in Windows Forms controls so you can render text the way you want and support international locales.

Miguel A. Lacouture

MSDN Magazine March 2006


Smart Clients: Build A Windows Forms Control To Consume And Render WSRP Portlets

  

Smart client apps use local resources, provide a rich client experience, and support intelligent install mechanisms. Web services offer powerful interoperability and integration features. Find out how to combine them to develop integrated apps that incorporate data from disconnected sources.

Carl Nolan

MSDN Magazine February 2006


Cutting Edge: Build Providers for Windows Forms

  

In ASP. NET and Windows Forms projects, some file types are treated differently than others. For example, ASPX and ASCX files are dynamically parsed and compiled to an assembly on the fly. The contents of an XML Schema Definition (XSD) file are used to create a new, strongly typed DataSet-based object at design time.

Dino Esposito

MSDN Magazine February 2006


Smart Clients: Craft A Rich UI For Your .NET App With Enhanced Windows Forms Support

  

The System.Windows.Forms namespace has increased by approximately 134 percent over the .NET Framework 1.1. There are 446 new public types; 113 existing types have been updated with new members and values; 218 types have been carried over from the original namespace. Read about it here.

Chris Sells and Michael Weinhardt

MSDN Magazine Visual Studio 2005 Guided Tour 2006


Spice It Up: Sprinkle Some Pizzazz on Your Plain Vanilla Windows Forms Apps

  

With the .NET Framework and GDI+, you can easily add elements of style to your applications. You can use transparency, irregularly shaped windows, notification icons, toast pop-ups, different color schemes, and lots more. Designed well, these techniques can create much more compelling interactions between your application and your users. This article explains how.

Bill Wagner

MSDN Magazine September 2005


Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend