How do I join ASP.NET mvc5 project and WPF project in one solution

Question

1.00/5 (2 votes)

See more:

i have two projects made separately. first project is made in asp.net mvc5 and second is made in wpf. i want to join them in one solution.
waiting for your kind response

What I have tried:

i have created mvc5 project and added wpf project in it. but not able to run or start wpf project from a web page.

Posted 19-Jul-18 22:43pm

Member 13919362

Updated 20-Jul-18 4:57am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard Deeming · Answer 1 · 2018-07-20T04:58:00

You won't be able to run or start a WPF application, or any other executable, from a web page. If you could, it would be a security nightmare!

You might be able to start the application from the code running on the server. But that will run the application on the server, where nobody will ever see it. There's very little point in doing that.

(It might appear to work whilst you're debugging your site in Visual Studio. But that's only because the client and the server are the same PC in that specific instance. As soon as you deploy to a real server, it will stop working.)