Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #11574 > unrolled thread

VO to WPF interop

Started byOskar Atkinson <Oskar@atk-it.com>
First post2018-05-02 11:53 -0600
Last post2018-05-09 23:27 +0200
Articles 8 — 5 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  VO to WPF interop Oskar Atkinson <Oskar@atk-it.com> - 2018-05-02 11:53 -0600
    Re: VO to WPF interop "Jamal" <noooospam@example.com> - 2018-05-02 14:03 -0400
      Re: VO to WPF interop Oskar Atkinson <Oskar@atk-it.com> - 2018-05-02 12:38 -0600
        Re: VO to WPF interop "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-02 20:43 +0200
        Re: VO to WPF interop nicktekhne@googlemail.com - 2018-05-03 13:50 -0700
          Re: VO to WPF interop Oskar Atkinson <Oskar@atk-it.com> - 2018-05-07 07:17 -0600
            Re: VO to WPF interop nicktekhne@googlemail.com - 2018-05-08 13:25 -0700
            Re: VO to WPF interop D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-05-09 23:27 +0200

#11574 — VO to WPF interop

FromOskar Atkinson <Oskar@atk-it.com>
Date2018-05-02 11:53 -0600
SubjectVO to WPF interop
Message-ID<oeujed1j3bqrf03fpojmgsf735ablflg8r@4ax.com>
Howdy,

I need to fire up a C# WPF view ( built using MvvmLight)  from VO. I know how to interface a  Winform C# dll via COM interop.
Is there any big difference with WPF?

Thanks
Oskar

[toc] | [next] | [standalone]


#11575

From"Jamal" <noooospam@example.com>
Date2018-05-02 14:03 -0400
Message-ID<pccui1$k2a$1@news.albasani.net>
In reply to#11574
Hi Oskar,

This is something that's interests me as well. I found the following which 
may help  (it's a 2010 post, but may still apply in VS 2017):

https://stackoverflow.com/questions/2186829/is-it-possible-to-package-wpf-window-as-com-object

Jamal

"Oskar Atkinson"  wrote in message 
news:oeujed1j3bqrf03fpojmgsf735ablflg8r@4ax.com...

Howdy,

I need to fire up a C# WPF view ( built using MvvmLight)  from VO. I know 
how to interface a  Winform C# dll via COM interop.
Is there any big difference with WPF?

Thanks
Oskar 

[toc] | [prev] | [next] | [standalone]


#11576

FromOskar Atkinson <Oskar@atk-it.com>
Date2018-05-02 12:38 -0600
Message-ID<q31kedl7gitisg9ehl3en1lhjd8f7utd4d@4ax.com>
In reply to#11575
Hi Jamal,

digging thru old posts, I just found a post from Nick Friend ( 2011) ... I hope he chimes in 
see below.

----
VO and Net interoperability
...
I have a Net component (done in C# with WPF) exposed as a COM
component and called in our VO app. This all works fine and is
straightforward, and I can call any required methods in the NET
component from VO.
-----


On Wed, 2 May 2018 14:03:42 -0400, "Jamal" <noooospam@example.com> wrote:

>Hi Oskar,
>
>This is something that's interests me as well. I found the following which 
>may help  (it's a 2010 post, but may still apply in VS 2017):
>
>https://stackoverflow.com/questions/2186829/is-it-possible-to-package-wpf-window-as-com-object
>
>Jamal
>
>"Oskar Atkinson"  wrote in message 
>news:oeujed1j3bqrf03fpojmgsf735ablflg8r@4ax.com...
>
>Howdy,
>
>I need to fire up a C# WPF view ( built using MvvmLight)  from VO. I know 
>how to interface a  Winform C# dll via COM interop.
>Is there any big difference with WPF?
>
>Thanks
>Oskar 

[toc] | [prev] | [next] | [standalone]


#11577

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-05-02 20:43 +0200
Message-ID<fkuf5uF1e4mU1@mid.individual.net>
In reply to#11576
Hi Oskar,

Nick is reading the forums on https://www.xsharp.info from time to time.

Wolfgang

Oskar Atkinson wrote:

> Hi Jamal,
> 
> digging thru old posts, I just found a post from Nick Friend ( 2011)
> ... I hope he chimes in see below.
> 
> ----
> VO and Net interoperability
> ...
> I have a Net component (done in C# with WPF) exposed as a COM
> component and called in our VO app. This all works fine and is
> straightforward, and I can call any required methods in the NET
> component from VO.
> -----
> 
> 
> On Wed, 2 May 2018 14:03:42 -0400, "Jamal" <noooospam@example.com>
> wrote:
> 
> > Hi Oskar,
> > 
> > This is something that's interests me as well. I found the
> > following which may help  (it's a 2010 post, but may still apply in
> > VS 2017):
> > 
> > https://stackoverflow.com/questions/2186829/is-it-possible-to-packag
> > e-wpf-window-as-com-object
> > 
> > Jamal
> > 
> > "Oskar Atkinson"  wrote in message 
> > news:oeujed1j3bqrf03fpojmgsf735ablflg8r@4ax.com...
> > 
> > Howdy,
> > 
> > I need to fire up a C# WPF view ( built using MvvmLight)  from VO.
> > I know how to interface a  Winform C# dll via COM interop.
> > Is there any big difference with WPF?
> > 
> > Thanks
> > Oskar 



-- 

[toc] | [prev] | [next] | [standalone]


#11578

Fromnicktekhne@googlemail.com
Date2018-05-03 13:50 -0700
Message-ID<1c5e5cd0-d6bf-4fef-8e41-ff4a9966e963@googlegroups.com>
In reply to#11576
Hi Oscar,

I still keep an eye on this forum from time to time, just for nostalgia's sake! It was ages ago that I did this WPF interop stuff, but I still have all the code somewhere... how can I help?

Nick

PS This would probably be easier on the XSharp forum.

On Wednesday, May 2, 2018 at 7:38:29 PM UTC+1, Oskar Atkinson wrote:
> Hi Jamal,
> 
> digging thru old posts, I just found a post from Nick Friend ( 2011) ... I hope he chimes in 
> see below.
> 

[toc] | [prev] | [next] | [standalone]


#11580

FromOskar Atkinson <Oskar@atk-it.com>
Date2018-05-07 07:17 -0600
Message-ID<1oj0fd18272l0na812jhkmvkdrb6b8qhlu@4ax.com>
In reply to#11578
Hi Nick,

I'll post here as Jamal seems to be very interested in the oissue as well - but I''l crosspost on the XSharp, too

I know who to interface a .net win32 C# dll from VO using COM interop. ( That is how I am firing up the Crystal reports, modify a report using the RAS API and fire up the viewer)

Now I need to fire up a WPF view that has an user control on it. I assume it is going to work in a similar way, probably a bit different how to pass an window handle from VO and how to deal with it in
the WPF side

So, any hints or sample surely are welcome :-)

Thanks
Oskar




On Thu, 3 May 2018 13:50:26 -0700 (PDT), nicktekhne@googlemail.com wrote:

>Hi Oscar,
>
>I still keep an eye on this forum from time to time, just for nostalgia's sake! It was ages ago that I did this WPF interop stuff, but I still have all the code somewhere... how can I help?
>
>Nick
>
>PS This would probably be easier on the XSharp forum.
>
>On Wednesday, May 2, 2018 at 7:38:29 PM UTC+1, Oskar Atkinson wrote:
>> Hi Jamal,
>> 
>> digging thru old posts, I just found a post from Nick Friend ( 2011) ... I hope he chimes in 
>> see below.
>> 

[toc] | [prev] | [next] | [standalone]


#11583

Fromnicktekhne@googlemail.com
Date2018-05-08 13:25 -0700
Message-ID<0c1dd334-c737-4e0e-af8a-b97440d8a4e7@googlegroups.com>
In reply to#11580
Hi Oskar,

I've replied on the XSharp forum....

Nick

[toc] | [prev] | [next] | [standalone]


#11587

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2018-05-09 23:27 +0200
Message-ID<aep6fd9j4uhomrhrl5fd4mhqeivich53ro@4ax.com>
In reply to#11580
Replying on message of Mon, 07 May 2018 07:17:32 -0600 from Oskar
Atkinson:


 Hello Oskar,

>I know who to interface a .net win32 C# dll from VO using COM interop. ( That is how I am firing up the Crystal reports, modify a report using the RAS API and fire up the viewer)


I used to start my VO program with a Vulcan created WPF screen, part
of a library which is used in my VO program and defined in the
manifest so it does not need registering.

On a certain moment - I am not sure if that moment was Windows update
based, or coincided with me (and some clients) starting to use 4K
monitors, starting with this window interfered with the SEUIXP toolbar
I use in VO: caption remained invisible for example.

After trying quite a few things which did not solve it I recreated the
window in VO. It looked a bit less "modern" but I could improve the
working faster and easier then I would be able to do in Vulcan/Visual
Studio. 

Don't let my conclusion withheld you from using non VO windows. My
aversion against VS is part of the reason and others may not share
that. But make sure you test the behaviour of the rest of the VO
interface well and also on a 4K monitor as I can't tell what caused
the problems for me.

Dick

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web