09-03-2010 11:19 AM
Anyone found a way (if there is a way) to access Unified Search through code compiled under 5.0?
One can dream ![]()
Having hard time justifying making a new build for just a single feature.
Seems like the only new thing is the unified search, everything else can be replicated on 5.0 and below devices, maybe some social additions (really no use for an enterprise developer).
09-03-2010 11:26 AM - edited 09-03-2010 11:27 AM
Hmn, I'm pretty sure its implementable using decoupled libraries which communicate solely through GlobalEvents or similar.
5.0 compiled app would check for presence of the class, if its present, it will start the 6.0 app. So the 5.0 doesn't throw verification errors. 6.0 library would still be able to be installed, it just wouldn't be able to run...
Going to try it ![]()
09-03-2010 12:23 PM
Not sure if that would work. For my Bing library I did a wrapper like feature:
This way on 5.0 (or earlier) it would say it isn't supported though it still needs a seperete compile.
09-10-2010 04:35 PM
It works.
09-10-2010 06:27 PM
Please explain to the crowd what you did ![]()
09-10-2010 06:49 PM
Implemented a bit differently, but allowed myself to keep a single build.
You have your main application check for 6.0 device being present and download and install the module with 6.0 support. 5.0 app controls 6.0 app through global events, which works out really great for Unified Search logic.
The idea is to completely decouple implementations into two separate apps so there is no library dependency and no verification errors ![]()
Basically what you described in your previous reply.
09-10-2010 09:01 PM
Well, I decoupled it but it still requires two builds of the library though from what you said you still need two builds as well, just they are not the same app/library.
09-10-2010 10:29 PM
Library only needs to be built under 6.0 to enable the Unified Search (can't build it under 5.0).
The core app is built under 5.0 to support all 5.0+ devices.
So in the essense we build two apps, but there is only one version/build for the core application.
Instead of having to build a 5.0 and a 6.0 version of the core applicaton, which brings a lot of overhead to QA/Sales/Support, etc. A tiny plugin makes it seem easy to the end user and non-dev crowd.
09-10-2010 10:51 PM
True
It would be a good thing to be able to do but I don't have a server that can be referenced for downloading a COD file that matches a specific OS.
09-11-2010 09:17 AM
I believe it would still install the 6.0 cod on a 5.0 device if you include it into a single jad batch.
It wouldn't be able to run on a 5.0 device, but it would install fine. As it's a tiny system module, the users wouldn't know any better either way.
No need for a server to host it, just bundle it ![]()