Then do new compilation in debug. Copy the deployed files up manually to your remote server. You basically want to ensure you have identical versions of all files on both your local machine and the remote machine. Show 1 more comment. Mike Blandford Mike Blandford 3, 4 4 gold badges 26 26 silver badges 31 31 bronze badges.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Helping communities build their own LTE networks. Podcast Making Agile work for data science. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked 2. Related Hot Network Questions.
Question feed. Stack Overflow works best with JavaScript enabled. Add a comment. Active Oldest Votes. Improve this answer. Vincent Vincent 61 1 1 silver badge 4 4 bronze badges. After having carried out a broad number of other suggested solutions Nevertheless, the question remains at large why the standard configuration fails that does not require pointing to the symbol file. I added a remote folder as the symbol file location.
But the breakpoint is still disabled. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Helping communities build their own LTE networks. Podcast Making Agile work for data science. The symbol files for mixed managed and native applications must be located on both the Visual Studio host computer and the remote computer. Apart from that, I've noticed that a ClickOnce application can provide the.
As soon as the project is an Office AddIn, the option to specify the files you want deployed is gone. Due to this limitation I switched most setup projects from ClickOnce to Wix.
0コメント