There are two potential methods I can think of off hand:
1. If the legacy app can adhere to COM standards, you can make a COM
callable wrapper around the .NET assembly and call that way
2. If not, you can wrap the .NET funcationality in a service and call the
service (Not sure how with POWER++, of course, if no SOAP functionality, you
will end up with a socket call)
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss
*************************************************
| Think outside the box!
|
*************************************************
"clintonb" <cbast2@xxxxxx> wrote in message
news:14a9e9f7-ae08-443a-bf5e-d160db63ac52@xxxxxx
Quote:
> At our company we have some old code written using Powersoft's Power++
> (a RAD C++ product). Power++ has been discontinued for quite a while
> now so we don't want to use it for new projects.
>
> We'd like to write a program in .NET that can be called by an old
> program we wrote in Power++. I'm assuming it is impossible to do that
> on the code level. Is there perhaps another way that a legacy .dll
> or .exe can call functionality in a .NET assembly?
>
> Usually all the stuff I see on the internet is about .NET code calling
> legacy code. And even then, it seems like it is calling .COM stuff or
> unmanaged Visual C++ code.
>