Communication between .NET 2 Assemblies and .NET 3.5 Assemblies
-
Hello, i have a .NET 2 Application (Class Library) and want to interact with a .NET 3 Application (WPF), how is this possible? Of course i could reference from the WPF-App to the Class-Library (thats the normal way) but i'm must be able to initiate the .NET 3 App from the .NET 2 Application. And of course they need to be able to communicate with each other... how can i do that? Why do i want to do that? Because i want to let my logic in the .NET 2 App and create a GUI-Layer in .NET 3.5 and one in .NET 2 (if the user doesn't have 3.5 or doesn't want it or want to use mono)
-
Hello, i have a .NET 2 Application (Class Library) and want to interact with a .NET 3 Application (WPF), how is this possible? Of course i could reference from the WPF-App to the Class-Library (thats the normal way) but i'm must be able to initiate the .NET 3 App from the .NET 2 Application. And of course they need to be able to communicate with each other... how can i do that? Why do i want to do that? Because i want to let my logic in the .NET 2 App and create a GUI-Layer in .NET 3.5 and one in .NET 2 (if the user doesn't have 3.5 or doesn't want it or want to use mono)
How about a three-part approach: - a 2.0 EXE with GUI - a 3.5 EXE with WPF-based GUI - a 2.0 DLL with all the logic, used by both EXEs. You can stuff these three projects in a single VS2008/10 solution, and set the target for each project separately. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly indented, and rendered in a non-proportional font; hint: use PRE tags in forum messages
-
How about a three-part approach: - a 2.0 EXE with GUI - a 3.5 EXE with WPF-based GUI - a 2.0 DLL with all the logic, used by both EXEs. You can stuff these three projects in a single VS2008/10 solution, and set the target for each project separately. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly indented, and rendered in a non-proportional font; hint: use PRE tags in forum messages
Yes, as i wrote that's the "normal" way. But i need to initiate the GUIs from the logic. Because the logic is used by a host as a "plugin" you can say. So i need to go that way.
Logic (2.0)---> WPF GUI (3.5) | | V WinForms GUI (2.0)So how can i do this the easiest way? -
Hello, i have a .NET 2 Application (Class Library) and want to interact with a .NET 3 Application (WPF), how is this possible? Of course i could reference from the WPF-App to the Class-Library (thats the normal way) but i'm must be able to initiate the .NET 3 App from the .NET 2 Application. And of course they need to be able to communicate with each other... how can i do that? Why do i want to do that? Because i want to let my logic in the .NET 2 App and create a GUI-Layer in .NET 3.5 and one in .NET 2 (if the user doesn't have 3.5 or doesn't want it or want to use mono)
I'm not sure there's any problem to begin with. Are you experiencing a problem? If so, what?
-
Yes, as i wrote that's the "normal" way. But i need to initiate the GUIs from the logic. Because the logic is used by a host as a "plugin" you can say. So i need to go that way.
Logic (2.0)---> WPF GUI (3.5) | | V WinForms GUI (2.0)So how can i do this the easiest way?You mean the logic must be the .exe file? Why? If you are just talking about callbacks, simply make the GUIs implement an interface defined in the logic assembly.