clickonce

问题 I've a project in .NET 4.0 that is published with click-once in local shared folder for testing. Once the testing passed we use mage.exe to resign the manifest and change publishing url with production final url http://www.ourcompany.net/.... Everything works if we use .NET 4.0. If we use .NET 4.5 and above, when we try to start application from the final url it fails to install with the error below. My question is: How should I use mage.exe to change the publication url of the application

问题 I created a ClickOnce deployment of my test application, and I am trying to run it on my Windows XP SP2 test box. When I click on the install button that Visual Studio 2008 creates, all I get is the manifest file displayed in my browser and it doesn't spawn the install. If I run the install against an Internet Explorer 7 test box, everything works OK. How can I fix this problem? 回答1: The first issue in the MSDN article Troubleshooting Specific Errors in ClickOnce Deployments addresses your

问题 We have an application that we want to make available to the general internet-using public with as few clicks as possible. I'm investigating whether we can use ClickOnce to avoid the confirmation dialog that our existing alternatives entail. My research so far indicates that this ought to be possible as long as (a) the application is AuthentiCode signes, and (b) it comes with a manifest that request a sufficiently innocuous set of permissions. Where can I find a detailed, authoritative list

问题 I've using ClickOnce and I'm struggling with file associations. I can set up the association. Double-clicking an associated file even launches the application. ...However... I don't know how to get access to the path of the file clicked to launch the App. Has anyone come across this before? 回答1: The official .NET way (w/o Registry) is to look at AppDomain.CurrentDomain.SetupInformation.ActivationArguments.ActivationData after startup. It is a string[] 来源： https://stackoverflow.com/questions

问题 I have a clickonce application which works fine on windows 7. When it's being installed on a windows 10 machine, it seems that the specific file for our application cannot be properly associated to the clickonce application. If I click right on the file, and choose "open with", I can see in the list "ClickOnce Application Deployment Support Library". But if I choose this option, I get a message saying "this application cannot be executed on your PC". If I decide to choose directly the .exe

问题 I've had a ClickOnce app in use for a few months now, but recently started getting an error on my deployment of the latest version. With this latest version I've added a reference to a DLL that I hadn't used before (FTD2XX_NET.dll if it's relevant), and suspect that this is related to the issue but I cannot figure out how to fix it. The actual project being deployed references another library project, which is what references the DLL (it references other DLL's but that has worked for months

问题 We decided to use the minimumRequiredVersion in our clickOnce application manifest, and now when we try to rollback to a previous version when the user launches the application it fails to start. It says the application manifest has a earlier version than the required version and the user can not use the application. We did not have this problem withou the minimumRequiredVersion, but we would like to use that. 回答1: You have to deploy a new version with a higher version number. There is no

问题 I try for several days now to publish my ClickOnce application with Azure DevOps Pipeline. Before going in detail here is what I would like to do from my release view: I started with one artifact and 2 release stage modifying the config.deploy file with staging variables during my Staging stage and modifying the config.deploy file with production variables during my Production stage. Deployment was working fine but installation of application was not working because of hash check system. So I

问题 i have developed an application in a .mdb access file with tables linked to sql server i try toput the mdb file in folder shared to all user but simultaneus access break the file very often. so iam trying to deploy the .mdb file to every client machine and keep it update. i have created a winform app that check mdb file version and copy it to a local folder and next opens the local copy but even in this way i have problem if too many user uses the winform launcher appat same time so iam

问题 Using Visual Studio 2008 Excel 2007 workbook customization using VSTO The error "Can't find project or library" recently began occurring in the Excel VBA editor on the following line of code: Property Get CallVSTOAssembly() As ShipdebitClaimProcessor.ThisWorkbook This only happens on clients using the published version. On my development PC it works fine. On the client in the VBE, under Tools, References, it says MISSING: ShipDebitClaimProcessor Location: C:\MyCompany\OfficeApplication\Excel