08-08-2013, 01:20 PM
Well, the idea behind building/publishing is that when you build an application, you pack everything into the .exe file and you can run the program from that .exe file.
As you stated, publishing creates a setup file that installs a ClickOnce variant of your application. What does this mean? Your application is installed in some crazy directory and has limited permissions (For example, the program can't directly be run as administrator). There is no difference in how the application actually runs, however.
In order to create a setup file, I usually build the application and have all of its dependent .dll files built to the same directory. I then build the setup file using NIS Setup Creator (Using the HM NIS Edit for a GUI). It creates really nice setup files.
Hopefully this resolves your issue.
As you stated, publishing creates a setup file that installs a ClickOnce variant of your application. What does this mean? Your application is installed in some crazy directory and has limited permissions (For example, the program can't directly be run as administrator). There is no difference in how the application actually runs, however.
In order to create a setup file, I usually build the application and have all of its dependent .dll files built to the same directory. I then build the setup file using NIS Setup Creator (Using the HM NIS Edit for a GUI). It creates really nice setup files.
Hopefully this resolves your issue.