Okay so for example I have 2 projects, Form1.exe & console1.exe, what I want is to execute console1.exe within form1.exe, so I used,
Now the problem with this is, in order to execute console1.exe the user must store that file locally, now the issue with that is, he/she can execute console1.exe without executing form1.exe
So what I did was used ILMerge to merge the .exe's as you would a .dll but it's unable to now find console1.exe, so merging didn't work.
So now my conclusion was to reopen visual studio & create a reference .dll out of console1.exe.
Problem with this is executing the .dll as if it were still a .exe without calling methods separately, so to execute the file as if it were one method.
So basically executing the parent class, which will then follow up with the sub classes.
Now is there anyway I can reference console1.exe and merge it to form1.exe preventing users from running it as a solo application, or is it possible to set rules on console1.exe that it may not execute unless called from form1.exe, or the second conclusion to run it as a .dll reference library in one command not multiple sub classes.
Code
if (isLogin(true))
{
MessageBox.Show($"Welcome!");
Process.Start("console1.exe");Now the problem with this is, in order to execute console1.exe the user must store that file locally, now the issue with that is, he/she can execute console1.exe without executing form1.exe
So what I did was used ILMerge to merge the .exe's as you would a .dll but it's unable to now find console1.exe, so merging didn't work.
So now my conclusion was to reopen visual studio & create a reference .dll out of console1.exe.
Problem with this is executing the .dll as if it were still a .exe without calling methods separately, so to execute the file as if it were one method.
So basically executing the parent class, which will then follow up with the sub classes.
Now is there anyway I can reference console1.exe and merge it to form1.exe preventing users from running it as a solo application, or is it possible to set rules on console1.exe that it may not execute unless called from form1.exe, or the second conclusion to run it as a .dll reference library in one command not multiple sub classes.


