The “VO-way” of programming does not work with WPF

Nov 21
2014
Comments Off

Today unfortunately I discovered that the “VO-way” of developing Windows applications does not work with WPF.

In VO, we used to paint a window in a separate application module, and to not write any code in this generated class. The hand written code was placed instead in a separate module, and in a subclass of the generated window. This separated first written code from generated one, and secondly it was easier to manage.

Unfortunately, WPF does not support such a (IMHO clean) style of programming, as XAML windows cannot be inherited.

I have found a document on MSDN on this subject:

MSDN:make a custom windows inherit from window

and it seems the way of using UserControls is the only remaining possibility to reuse paintend windows.

Written by wriedmann in: Vulcan.NET Programming |

WPF applications with VIDE

Nov 21
2014
Comments Off

Since I like VIDE more than Visual Studio, I would continue to use it also on WPF programming with Vulcan.NET.

Unfortunately, VIDE does not support XAML, since it has no XAML editor integrated, and it does not compiles XAML to BAML. At the moment, Chris Pyrgas, the author of VIDE, is searching ways to integrate both a XAML editor and the compiling of XAML to BAML into VIDE.

But fortunately there are methods to accomplish this now. At this moment, I know 3 of them that work, the 4th that would be my favorite one, unfortunatley does not work:

1) don’t use XAML and construct all windows in plain Vulcan code. It gives more flexibility creating the windows, but it seems it willbe more work.
2) create the windows in Visual Studio or Blend, creating C# code. All the other code used for MVVM can be written in Vulcan.NET using VIDE. This was discovered and tested by Frank Maraite who will be able to give also samples.
3) Chris Pyrgas has showed another method: create the windows in Visual Studio as Vulcan.NET projects. Then add the code-behind files as source code files to the VIDE project, and also the VS-compiled resource files as external resources. A sample for this can be requested.
4) this (unfortunately not working) method is called by me “The VO way”, as it uses concepts from Visual Objects. The windows are created in Visual Studio, maybe as based on classes created in VIDE, and compiled to a DLL. Without writing any code, the application itself is written in VIDE, with the VS generated DLL as dependency, and the used windows are inherited from the ones written in Visual Studio. Unfortunately, this method does not work, as the WPF does not support inheriting from a XAML window.

Written by wriedmann in: Vulcan.NET Programming |

552 5.3.4 Message size exceeds fixed maximum message size – SBS 2011

Nov 06
2014
Comments Off

Recently, I had problems with an SBS 2011 Server where the Exchange 2010 does not accepted mails with more than 10 MB (the default limit), and fetchmail returned an

552 5.3.4 Message size exceeds fixed maximum message size

error.
I have changed the limit everywhere (Organisation and Server properties), but not on the Windows SBS 2011 Fax Sharepoint connector, but it does not worked until I changed this also on the SBS 2011 Fax Sharepoint connector.

Written by wriedmann in: Uncategorized |