Hi,

I was wondering if someone here has some experience with the deployment of a winform application which depends on DO4.0? Are there any special things I should take into account?

Do I need to install DO4.0 onto the target machine or is adding the required assemblies into the GAC enough?

Hopefully someone can help me...

Regards, Martijn

Updated at 08.12.2009 20:49:03

Hi,

Thanks for the reply, I did some setup building today with the standard setup projects shipped with vs2008 and things seem to work fine. Tomorrow I do some more advanced setup building based InstallShield.

Btw, how do you deal with data binding on WindowsForms? Currently we support just WPF interfaces (INotifyXxx), there is no support for WF interfaces (IBindingList, IEditableObject, etc.) so far.

Well I must say and not very good at designing client interfaces, not my core business :D
For this project I use DevExpress components in my WindowsForms and custom IBindingLists, IEditableObjects which are set as the datasource for the grids, comboboxen, etc I use to show output to the user.

Or is this not what you mean?

Regards

Updated at 09.12.2009 22:23:03

Ok for example,

I have a lookup edit (DevExpress component) which has a so called datasource propertie

lookupedit1.datasource = myservice.getCountries();

myservice looks like this,

public class myservice:sessionbound
{
     public List<string> GetCountries()
     {
          List<string> result = new List<string>();
          var countries = Query<Country>.All;
          foreach(var cnt in countries)
          {
              result.add(cnt.name);
          }
           return result;
     }
}

For textbox binding I do the following,

var myObject = myservice.GetObjectDetails(code);
textbox1.text = myObject.Name;

public class myservice:sessionbound
{
     public myObject GetObjectDetails(string code)
     {
          return (from o in Query<myObject>.All
                   where o.code == code
                   select o).Single();
     }
}

I track the text changes made by the user by setting a boolean value, if the value is true then text is changed by the user. When the user saves his changes I again call myservice. See example

public class myservice:sessionbound
{
     public bool Update(myObject, string code, string name)
     {
          var o = myObject;
          o.code = code;
          o.name = name;
     }
}

I know this is not the most fancy way but It works for me for now. I due hope proper winform binding is implemented in a later release of DO4.0

This any help??

Updated at 10.12.2009 21:19:04

About binding for WindowsForms: are there any issues we can eliminate quickly? I.e. what would you like to get ASAP here?

At this point I don't have any major issues regarding binding objects within my application...because I don't use IBindingList, IEditableObject, etc. But I will do some research regarding binding doa objects to WindowsForms the upcoming day's. Will keep you posted.

Regards

Updated at 15.12.2009 10:56:26

Ok I did some searching on the internet about IEditableObject, INotifyPropertyChanging, INotifyPropertyChanged and come across a nice article by Paul Stovell, http://www.paulstovell.com/editable-object-adapter This article talks about a wrapper around a "data-bound object".

But would it work on DOA object?? Well I think it does..with some alterations, mostly error catching :D

The attached file contains a project with winform bindings, check it out and see if this is what you mean. I hope this will help you develop winform bindings support in DOA4.0

Regards, Martijn

Updated at 16.12.2009 15:35:34

Let me do some more testing regarding

• Base -> Adapter<base>
• Descendant -> Adapter<descendant>

I think modifing the properties of a Descendant through a adapter<base> is going to difficult...maybe imposible, will keep you posted.

Btw what do you mean by

but earlier we didn't invent a "complete" way allowing to adopt it here, and, likely, because of that we didn't try to evaluate it.

Cheers

This thread was imported from our support forum. The original discussion may contain more detailed answer.