Researched on this and found that it’s because of target platform x86. this version will only work in x64 target platform of widows application. So changed target platform of windows app to x64 and able to run successfully in local.
But we got an issue in installation. So we changed setup project target platform to x64 and we are adding three primary outputs to setup project. one windows application and two windows services because when ever we are installing this application, it will install windows app and two windows services in background. So we changed windows services target platform to x64 as well able to build setup project successfully after newly added things which are build under x64.
But still we are facing below issue
Hi, @borrrden, We tried using x64. We did Re build of all projects under x64 and added new output to setup project. did we missed anything? is there any other ways to overcome this issue.
I can’t really be sure where the issue is coming from without seeing it myself. The exception is saying that something is still not x64 and that’s basically all the information present. Maybe you can use dependency walker or something to go through all of its dependencies.
HI @borrrden, We created a new project, it contains windows application and setup project. Still we are getting same issue in new sample project. please go through the link where attached new sample project. WindowsFormsApp.zip
I don’t have the tooling installed to run the vdproj (in fact I’ve actually never even heard of such a project). However, the app runs fine for me. I notice, however, that release mode has “prefer 32-bit” enabled which could be an issue.
I was able to install the vdproj tooling and see the issue but I have no insight into what causes it. The project runs just fine and it seems like it is a problem specifically with that tooling.
