Posts


I ran across a great .net project called Eto. It is basically “a cross platform desktop and mobile user interface framework” that is similar to xwt but more mature and supporting more platforms.

I have been testing the winforms and wpf back ends and they seem to work great. It also has a mac and iOS back end that appear to be fully functional. An android back end is planned for the future and I am currently investigating this.

It would be great if I can write the majority of my .net user interface code using one library and have it run on desktops and mobile. The only thing that would be lacking is windows rt support.

To start developing with Eto download the binaries from https://github.com/picoe/Eto/downloads. Add the reference to your project and start programming. See https://github.com/picoe/Eto/wiki/Preparing-your-solution for more details to setup your project.

Screen Shot:

VB.NET First App Example

Imports Eto.Forms
Imports Eto.Drawing

Class MyForm
    Inherits Form

    Public Sub New()
        Me.Title = "My Cross-Platform App"
        Me.Size = New Size(200, 200)

        Dim label = New Label()
        label.Text = "Hello World!"

        Me.AddDockedControl(label)
    End Sub

    <stathread> _
    Public Shared Sub Main()
        Dim app = New Application()
        AddHandler app.Initialized, Sub()
                                        app.MainForm = New MyForm()
                                        app.MainForm.Show()
                                    End Sub

        app.Run()
    End Sub

End Class

C# First Example App

using Eto.Forms;
using Eto.Drawing;

class MyForm : Form
{
	public MyForm()
	{
		this.Title = &quot;My Cross-Platform App&quot;;
		this.Size = new Size(200, 200);

		dynamic label = new Label();
		label.Text = &quot;Hello World!&quot;;

		this.AddDockedControl(label);
	}

	[STAThread()]
	public static void Main()
	{
		dynamic app = new Application();
		app.Initialized += delegate 
		{
			app.MainForm = new MyForm();
			app.MainForm.Show();
		};

		app.Run();
	}

}

https://github.com/picoe/Eto https://github.com/mono/xwt


I have been working on MyFyiReporting lately. There is a new wiki page describing how to use barcodes and qr codes (https://github.com/majorsilence/My-FyiReporting/wiki/Barcodes-and-QR-Codes).

I have also spent some time working on the reporting server. See https://github.com/majorsilence/My-FyiReporting/wiki/Reporting-Server for a more detailed info. Basically it is a site where users can view reports online.

If you check out the Issue11PdfUnicodeCharacters branch you will see I have finally merged in the iTextSharp fixes that allow cyrillic character support.


I have started putting together some nuget packages for My-FyiReporting. This should make it easier for those that wish to use the viewer or designer in their projects to setup everything.

At the moment I have the x86 package created. It includes .NET 3.5 and 4.0 dlls and will auto setup for your project type. See https://nuget.org/packages/My-FyiReporting.x86.

I do not have the 64 bit package created yet but when it is created you should be able to get it from https://nuget.org/packages/My-FyiReporting.x64

These packages are a work in progress and currently still need a little work to make them perfect.


My-FyiReporting 4.5.2 has been released.

The main new features and bug fixes are:

  • RdlReader opens maximized and if only one report opened it opened it opens maximized
  • RdlReader can open files with command line arguments, allows dragging report onto reader icon to open report
  • RdlReader switched to toolstripmenuitem
  • RdlReader now has a toolstrip with open, print, and save as button
  • Icons upgraded to newer tango icons where possible
  • Some new copy right info added
  • Fix missing references
  • Several bug fixes in reader and asp project

Download: https://github.com/majorsilence/My-FyiReporting/downloads


I have decided to fork WarSetup. This is because it has not been updated in several years and was lacking some features that I needed.

I could switch to other software but I like warsetup and would prefer to continue using it. So until the main project starts releasing updates again I will be keeping my fork at https://github.com/majorsilence/WarSetup-Fork.

I have renamed the executable to WarPackager so there is no confusion between the main WarSetup and my fork.

Current added features WarPackager has over the main WarSetup are:

  • Wix 3.6 support
  • Wix 3.5 support
  • OS requirements detection XP SP3, Vista SP1 and SP2, Windows 7 and SP1, Windows 8
  • Option to require minimum .NET version (2.0, 3.0, 3.5, 4.0 full or client)
  • Command line arguments
    • -i "warsetup file to use.warsetup"
    • -c - compile msi automatically
    • -v "new product version number in format 1.1.1"
    • -a - auto increment version number before build and save
    • -e - auto exit after build

Download page: https://github.com/majorsilence/WarSetup-Fork/downloads