Note that there are some explanatory texts on larger screens.

plurals
  1. POAppHarbor WPF ClickOnce
    primarykey
    data
    text
    <p>I have an open source WPF application hosted on GitHub: <a href="https://github.com/tomhunter-gh/SourceLog" rel="nofollow">https://github.com/tomhunter-gh/SourceLog</a></p> <p>What I was hoping to do was add ClickOnce deployment and host the ClickOnce install on AppHarbor so that users are automatically upgraded when I push new commits to GitHub. What I'm looking for is an auto update feature similar to the GitHub Windows client, and I'm also hoping to find somewhere to host the ClickOnce install bits for free.</p> <p>I have a number of questions:</p> <ul> <li>How does AppHarbor actually work? As far as I can tell it expects a Visual Studio solution containing a single web application project, which it then builds and "deploys". What specifically does it look for to run, what assumptions is it making? What happens when you have non web projects, or your solution isn't in the root directory for example? </li> <li>Is there any way to customise the build and deployment process, for example with custom MSBuild scripts?</li> <li>How would I ensure the WPF project is "published" so that the ClickOnce bits are generated?</li> <li>Is there any way to get a build number from the AppHarbor build process? E.g. a four part assembly version 1.2.3.4 and write that to the generated binaries/config?</li> <li>Is there any way for AppHarbor to push the ClickOnce bits back to GitHub after a successful build, so that I could instead host the ClickOnce install on GitHub?</li> </ul> <p>Should I be taking a completely different approach?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload