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?
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?
If you have any questions, feel free to write us.
Regards
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.
Hello Jorgen,
Thanks for the details. I understand your point of view and I think that you have good arguments.
jorbjo said: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 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.
I`m not familiar with your scenario, but maybe one possible approach to avoid any unnecessary transformation, could be if you are using binary data. What I mean ? Our appointments has a property with name "AllProperties". This property contains all information (all settings) about your appointment and this information could be stored in database in a Binary format. You could read this binary data from database and transfer through the WCF service direct to your WinForms Client in a Binary format. On your Client Side you could convert your Binary data back to Appointment . For example:
Appointment App = Appointment.FromBinary();
or
Appointment App = Appointment.FromBytes((byte[])myReader[0]);
For the opposite process, you could save your Appointment back to bites on your Client side and transfer these data back to database. The disadvantage of my suggestion is when you need to operate with these appointments on a business layer, that why I`m agree with your arguments.
jorbjo said:I also want the dll i reference to be as small as possible. hence no GUI Controls/Components serverside nor in the WCF contract.
There are many benefits to submitting an product idea:
- Direct communication with our product management team regarding your product idea.
- Notifications whenever new information regarding your idea becomes available.
- Ability to vote on your favorite product ideas to let us know which ones are the most important to you. You will have ten votes for this and can change which ideas you are voting for at any time.
- Allow you to shape the future of our products by requesting new controls and products altogether.
- You and other developers can discuss existing product ideas with members of our Product Management team.
Steps to create your idea:
1. Log into the Infragistics Product Idea site at http://ideas.infragistics.com (creating a new login if needed).
2. Navigate to the product / platform channel of your choice (e.g. WPF, Windows Forms, ASP.NET, HTML5 / Ignite UI, iOS / NucliOS, etc.)
3. Add your product idea and be sure to be specific and provide as much detail as possible. Explain the context in which a feature would be used, why it is needed, why it can’t be accomplished today, and who would benefit from it. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it. Be convincing!
The Product Idea site puts you in the driver’s seat and allows you to track the progress of your ideas at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
I thought of Another argument:
What If you have several different GUI clients. WindowsForms, WPF, Windows Phone etc. They have different Controls but the Appointments Object should be the same no matter what client you use, shouldn't it?
For now my WindowsForms Client is intended for a Desktop/Laptop but in the future I might want to add a Tablet or a Phone app or a touch screen app. They should be able to consume the same WCF Service.
On Another note. They are not stored as appointments in the database. I have stored the properties as separate database columns so that I can use the data in other ways than through ultrawinschedlule.
Please use the link to create a new product idea http://ideas.infragistics.com
Let me know if you have any questions.