Hi John, Unfortunately it's hard to maintain 2 separate solutions with a bunch of similar projects linking files. Everytime you add a file you have to switch and create a link. You might use Project Linker (from P&P), although I never got it to work. Another solution is to simply have a NANT script, a post build action or some MSBuild voodoo to builds the same project for WP7. I've seen many OS projects go down that path. Ninject is one that comes to mind.
On Mon, Sep 27, 2010 at 12:40 PM, John OBrien <j...@soulsolutions.com.au>wrote: > Guys, any experiences or suggestions for developing a Silverlight control > that you'd like to run on both Silverlight 4 and Phone 7? > > Having looked at it currently we are planning to: > > > 1. Have two Solutions, A Silverlight 4 and a Phone 7, replicate > projects, same namespaces but different assembly names. > 2. Have all the code in the Silverlight 4 solution / projects. Phone 7 > projects will have code files added as a link to the SL4 files. > 3. For the core anything not compatible with Phone 7 surround with #if > !WINDOWS_PHONE > 4. Break apart anything really specific into different projects, simply > don't have them in the Phone or Silverlight4 solution. Eg specific drop > target feature for Silverlight4 only > > > Major issue we see with this is that you can easily add something to the > Silverlight4 solution that will break the Phone7 solution, looking at a > build server that would build both solutions and report these errors > quickly. > > Thoughts? > > _______________________________________________ > ozsilverlight mailing list > ozsilverlight@ozsilverlight.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > > -- Miguel A. Madero Reyes www.miguelmadero.com (blog) m...@miguelmadero.com
_______________________________________________ ozsilverlight mailing list ozsilverlight@ozsilverlight.com http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
