VS 2010 XAML editor doesn't respect references added by means of openwrap
Opened this issue · 4 comments
Is that after a build once the packages have been added?
Sent from my iPhone
On 9 Sep 2011, at 14:51, "Ivan" reply@reply.github.com wrote:
Reply to this email directly or view it on GitHub:
#237
yes. It is persistent issue.
This is a big one for our team as well. Trying to use a wrap containing user-control assemblies for consumption in WPF xaml is a huge priority and does not work at all currently.
The change required to support adding references statically instead of the current dynamic system is rather large, there is no way this is going to make it in 2.0.3 from me.
If someone wants to have a try, I'm happy to provide guidance as to how it can be done. If someone wants to sponsor that feature for inclusion at 2.0.3 that's also something we can investigate.
That said, there's a temporary way we can solve this problem, with many constraints (no support for updating without vs running, hacking around msbuild files...) but that would get broken if and when the proper static way is used.
It involves making the projects that want static injection not assign references, and add a solution plugin that monitors the global assembly list changed event and add those refs to the dte when things change.
Sebastien Lambla
On 14 Jun 2012, at 19:06, "mikebev" reply@reply.github.com wrote:
This is a big one for our team as well. Trying to use a wrap containing user-control assemblies for consumption in WPF xaml is a huge priority and does not work at all currently.
Reply to this email directly or view it on GitHub:
#237 (comment)