Using WPF with a "normal" windows app

  • Thread starter Thread starter Lloyd Sheen
  • Start date Start date
L

Lloyd Sheen

I was wondering if there is any way to incorporate a WPF form within an
existing windows app.

Have googled but this is the type of question that is hard to phrase to get
results.

Alternative if it won't work is to create a form with a browser control and
generate HTML but that is not the route I want to go since it will not be
very easy to maintain.

Thanks
LS
 
Lloyd Sheen said:
Thanks will try that,

LS

Well this did not go well. I get to step 5 in the instructions before it
falls apart. I can create the WPF Browser Application but cannot change the
Output Type. This is so MS typical.

I guess it cannot be done. Oh well maybe in VS 2050.

LS
 
Lloyd Sheen said:
Well this did not go well. I get to step 5 in the instructions before it
falls apart. I can create the WPF Browser Application but cannot change
the Output Type. This is so MS typical.

I guess it cannot be done. Oh well maybe in VS 2050.

LS

I did find this link if anyone is interested. It describes (correctly) how
to do this.

http://www.a2zdotnet.com/View.aspx?id=78

LS
 
It can definately be done, but it's certainly not simple. For instance, I
have a Windows Forms app that uses WPF to display a panning tilting rotating
blinking textured 3D view of my data and it's very effective.

Note however, that a lot of the documentation is out of date due to the
significant changes that have occurred over its life, and you need to
consider which version any example was used with. I also find it very
annoying that so few examples use VB - you will need to have a C# to VB
converter available if you want to use the example code, and you need to
allow for any differences in IDE setup.

And the documenation for XAML is lousy.
 
Lloyd Sheen said:
snip <

I did find this link if anyone is interested. It describes (correctly)
how to do this.

http://www.a2zdotnet.com/View.aspx?id=78

LS
I guess I should have made the point that the MS documentation is patchy,
and you needed to follow on through the references from that page, and to
whatever else the keywords there might lead you to. It's possible that the
samples and description aren't a lot worse than other parts of MSDN, but I
noticed a steeper than usual learning curve, if only because almost
everything is in C# rather than VB. This applies to other sources, not just
MS. Needing to get to grips with XAML didn't help.
 
Back
Top