The module I am developing is designed the way that all our features (employee list, employee profile birthday list, telephone list, job list, job profile, request name card form, preview name card, etc.) are in one module in different Asp:View elements and depending on the module settings the selected view is being displayed. Now this causes the following problem:

When the print button of the module is clicked, the print version of the Asp:View which is selected in the module settings is displayed, although a user already might have navigated to another view by some links. E.g. a user starts at the name card request form because in the module settings it is selected to display this Asp:View. When he submitted his name card request, another Asp:View for showing his name card preview will be set to visible. When he now wants to print his sample name card, the window with the print view will show the name card request from instead of the Asp:View where he navigated to.

I guess it is because in the page_load event I am retrieving the view to display from the module settings so the print function will always use that view to display being printed although I might already be on another view where a user usually will get with links and GET parameters. The print button is a JavaScript function and does obviously not include the GET paramters which are currently part of the URL but only the module tab/page so always the default view from the module settings is loaded. So how can we correct this?

Is it furthermore possible to define the area of the module to be displayed for printing? E.g. in the name card preview example, on the name card sample should be displayed, while some other information (date of request, status of workflow etc.) can be skipped.

As it is a Skin Object I guess it is used in the whole site skin so will apply to the whole site but not only my module. Or is it possible to use a Skin Object within a module, too?

Sebastian, I tried the skinobjects, let me describe my experiences, because it confuses me:

1. Both skinobjects (PAGEPRINT and TEMPLATEPRINT) did not install correctly; while their files were installed in DesktopModules/Vendorname/Control.ascx, the module definition in host pointed just to Control.asx.
2. So I changed the module definition from control.asx to DesktopModules/Vendorname/control.ascx and the TEMPLATEPRINT was working great!
3. Today I turned on my testing machine again and built my lcoal test environment. I went to Host > Extensions to install another module and so an error message which comes from the TEMPLATEPRINT skinobject. I did not change anything, the module definition still points to the correct folder and file, and even un-installing and re-installing the Skinobject does not change anything. Error msg:

DotNetNuke.Services.Exceptions.ModuleLoadException: startIndex cannot be larger than length of string. Parameter name: startIndex ---> System.ArgumentOutOfRangeException: startIndex cannot be larger than length of string. Parameter name: startIndex at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy) at VMasanas.DNN.SkinObjects.TemplatePrint.TemplatePrint.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

4. While in the module definitions and extensions it is showing that error message, all normal pages have the print button and the template print works fine, module settings do not show a print button but no error message.