MultiTargetting WPF / Silverlight
-
Hi All, Long time since I posted here! Hope we're all well. I'm literally on my last day on my current contract and this topic has just been floated!! I've built a PRISM / WPF / R based application for this contract and they have decided to investigate offering it as a web based thing as well. Anyway, I've just been having a play with Project Linker and so far I'm seeing it as more of a hinderance than a benefit. Yes it does some fiddling for you but the fact that it will only work WITHIN a single solution (as far as I can tell) is a tad annoying. I think I'd prefer to have two solutions and manage the linking manually. Crazy??? I've got the team here using ReSharper and it's frankly rendered that more or less useless in terms of reporting false positives on the solution wide analysis. It's annoying already on a tiny test project with two class files! Moving this into production on the app would be a nightmare! Does anyone have any practical tips or suggestions for using Project Linker in a more useful manner. Right now I'm leaning towards careful manual management of linking files that we want to reuse in both WPF and Silverlight. If I'm slightly annoyed by it already moving this into production will only compound that imho ... Jammer
-
Hi All, Long time since I posted here! Hope we're all well. I'm literally on my last day on my current contract and this topic has just been floated!! I've built a PRISM / WPF / R based application for this contract and they have decided to investigate offering it as a web based thing as well. Anyway, I've just been having a play with Project Linker and so far I'm seeing it as more of a hinderance than a benefit. Yes it does some fiddling for you but the fact that it will only work WITHIN a single solution (as far as I can tell) is a tad annoying. I think I'd prefer to have two solutions and manage the linking manually. Crazy??? I've got the team here using ReSharper and it's frankly rendered that more or less useless in terms of reporting false positives on the solution wide analysis. It's annoying already on a tiny test project with two class files! Moving this into production on the app would be a nightmare! Does anyone have any practical tips or suggestions for using Project Linker in a more useful manner. Right now I'm leaning towards careful manual management of linking files that we want to reuse in both WPF and Silverlight. If I'm slightly annoyed by it already moving this into production will only compound that imho ... Jammer
A word of caution, mate, from the dark side of having done this in the past. If you haven't designed your application for multi-targetting from the get go, there are all sorts of little incompatibility issues that crop up and bite you. The reason is simple - Silverlight is not WPF. WPF provides features that just aren't available in Silverlight, so if you've used any of those features, you have rework to do.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
A word of caution, mate, from the dark side of having done this in the past. If you haven't designed your application for multi-targetting from the get go, there are all sorts of little incompatibility issues that crop up and bite you. The reason is simple - Silverlight is not WPF. WPF provides features that just aren't available in Silverlight, so if you've used any of those features, you have rework to do.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
Hey Pete, Yeah, this I've heard from a number of people and in my write up on this topic I've prepared them for building sufficient time into the project going forward for re-tooling. Luckily we have used PRISM which should help a little and we already have a good set of 3rd party controls from a single supplier (Infragistics) for both platforms which should at least provide some look and feel consistency. I've also suggested doing some spikes first to get a better feel for a more accurate effort commitment that may be required. Based on that the next step would be to convert to multi-targetting and only then start the next phases of development. Project Linker is not my friend!!! ;) Jammer
-
Hi All, Long time since I posted here! Hope we're all well. I'm literally on my last day on my current contract and this topic has just been floated!! I've built a PRISM / WPF / R based application for this contract and they have decided to investigate offering it as a web based thing as well. Anyway, I've just been having a play with Project Linker and so far I'm seeing it as more of a hinderance than a benefit. Yes it does some fiddling for you but the fact that it will only work WITHIN a single solution (as far as I can tell) is a tad annoying. I think I'd prefer to have two solutions and manage the linking manually. Crazy??? I've got the team here using ReSharper and it's frankly rendered that more or less useless in terms of reporting false positives on the solution wide analysis. It's annoying already on a tiny test project with two class files! Moving this into production on the app would be a nightmare! Does anyone have any practical tips or suggestions for using Project Linker in a more useful manner. Right now I'm leaning towards careful manual management of linking files that we want to reuse in both WPF and Silverlight. If I'm slightly annoyed by it already moving this into production will only compound that imho ... Jammer
Jammer wrote:
I'm literally on my last day on my current contract and this topic has just been floated!!
I see a contract extension in the offing. Really on the LAST day!
Never underestimate the power of human stupidity RAH