Appointments in a separate dll? | Infragistics Forums

340

Appointments in a separate dll?

Jörgen posted over 10 years ago

I have a multilayerd application where I want to read data from the database and display it in a ultradaywiew Control.

In my business logic layer I want to convert from a data table to an appointments Collection. to do this I need access to Infragistics.Win.UltraWinSchedule.dll

This DLL contains GUI Components specific for WindowsForms which I don't want to have in my Business Logic layer on the server.

Is there a way to get the NON-GUI parts of UltraWinSchedule in a separate DLL so I don't have to reference the whole UltraWinSchedule.dll serverside?

Parents

No Data

Reply

53790

Georgi posted over 10 years ago

Hello jorbjo,

jorbjo said:
Is there a way to get the NON-GUI parts of UltraWinSchedule in a separate DLL so I don't have to reference the whole UltraWinSchedule.dll serverside?
I`m not sure that I understand very well your final goals and benefits of removing GUI parts of this assembly (what is the issue if you are using our current assembly), but to be honest I think that this is very complicate task, that could cause a lot of damages, so I don`t think that our Product Management Team will take a such decision. Could you please explain us more deeply what is your issue and we will try to help you.

If you have any questions, feel free to write us.

Regards
Cancel
Reply

Cancel

Children

340

Jörgen posted over 10 years ago in reply to Georgi

I have a WindowsForms Client talking to a Server app via a WCF Service.

I would like my server app to read from a database and build an AppointmentsCollection and send it to the Client app where I consume it in a form with a UltraDayView Control.

Today I have to reference the Ultrawinschedule.dll in my server app and my WCF Contract. They both are non GUI and should not have access to GUI Components such as the UltraDayView Control.

I also want the dll i reference to be as small as possible. hence no GUI Controls/Components serverside nor in the WCF contract.

Only The Appointments, AppointmentsCollection (and any dependencies) should exist both serverside and clientside.

Today I have made a temporary solution where my WCF service returns a BindingList and then I have to transform it into an appointmentsCollection client side. When I want to save my Changes the client has to transform it back to a bindinglist Before sending it to the WCF service. The Server app then has to transform it again Before saving it to the database.

I would like to avoid any unneccessary transformations which I can do by letting the WCF service return an AppointmentsCollection.

On the other hand I don't want to have references to GUI Controls serverside and in my WCF Contract.

Having the UltrawinSchedule.dll as is, is fine when you have a standalone WindowsForms app but not suited for a Multilayered Client/Server app,

Also We have a policy against having GUI Components serverside.

I hope this clarifys my issue/Point of View.
Cancel
Reply

Cancel