I have a fully developed windows desktop application. Unfortunately, we were forced to upgrade our 3rd party control, developer express ([login to view URL]) and the migration from 2006 to 2009 has not been so straightforward. We have gotten over many of the hurdles, but one still remains.
However, before considering this job, the code was written using Microsoft Application Blocks - Smart Client Application Block Library. Given that, self evaluate yourself to realize whether or not you would consider yourself to be an expert within this type of coding. If you do not believe yourself to be one, this job probably is not for you. Additionally, you must be extremely proficient using DevExpress XPO, retain your own license, and have incorporated an upgrade from 2006 to 2009 or you will be severely disadvantaged.
The problem with the current state of the application is that there is policy functionality that is not being recognized and incorporated when using a direct connection between one application (the book) and another (the player). While it does appear that the direct connection itself can be established, the policy that becomes associated with that direct connection is failing. I need this corrected and my understanding is that the problem stems from the following:
Relating specifically to the current problem, it stems from the way the program uses XPO to relate objects in parent child relationships. When a parent object such as a player is loaded, related child objects such as policy are supposed to be loaded as well. This is not happening and it is either due to the code, the wrong implementation of XPO, or perhaps (but unlikely) a DevExpress bug or issue. One of the central “improvements?? of DevExpress since the 6.3 version the app was built with, deals explicitly with relationships and nested collections. The evidence is strongly suggestive that XPO Collections in the domain layer are where additional problems reside.
Some reference material that any developer would want to look at can be found at
[login to view URL]
A video of this issue may be found at this link: [login to view URL]
## Deliverables
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
[][1]
## Platform
Windows XP, Vista, 7