I have SKD project Net461. VS 2019. And I dont have options to publish ClickOnce like it look like in: https://learn.microsoft.com/en-us/visualstudio/deployment/quickstart-deploy-using-clickonce-folder?view=vs-2019
I was looking for a component in VS installer and I find only one: "Publishing with the ClickOnce application".
I have only this:
And I don't have a publish tab in Project Properties.
Not through the IDE, but I was able to put ClickOnce in a WPF net48 project with new SDK style to run in an easy way when using msbuild /t:publish.
More info at https://stackoverflow.com/a/69583858/4386359
Related
How can I publish my Outlook Addin project from my solution(I don't want to publish all my solution) from command line tools(MSBuild)?
Furthermore I'd like to use TeamCity to publish this OutlookAddin(just this project from solution).
THX.
I think you can find the information you need here;
How to build an Office Add-In without registering it on the build system?
TeamCity supports MSBuild configuration steps, so once you get the MsBuild setup correct, getting TeamCity to build your addin should be straightforward.
When i build my project VisualStudio creates allso a file names MyProjectName.application. What is this file used for? How can i disable the creation of this file in VisualStudio?
Using VisualStudio 2010.
In older versions of visual studio (<2010) you would deploy your application using Setup Wizard but ClickOnce is newer and preferred way of deployment. For ClickOnce deployment model .application files are default deployment manifest for your application i.e they have all the information regarding the choices you make when you deploy your application using ClickOnce. You can find more information here and here
To disable ClickOnce, open your project's properties and do following:
Under Signing tab, uncheck "Sign the ClickOnce manifests".
Under Security tab, uncheck "Enable ClickOnce security settings".
after that delete .application file and it should not reappear.
.application files are default deployment manifest for ClickOnce applications.
I am trying to deploy an app in C# with a Setup And Deployment project in VS2010. The main project and the deployment project are in the same solution and I have added the primary output of the main project to the deployment project. In the property pages for the deployment project, there is a button for prerequisites. How do I find out what items my app will require for successful deployment?
Thanks.. :)
Visual Studio will manage all the requisite DLL's that need to be installed for your application to run... If still you need to add more dependencies then you could create an application that will handle this process for you.
And since Microsoft has an easy solution for almost everything, there are options to the installer to do just this. Here you'll find it as per MS documentation.
Right click your project => propereties => Application => Target Framework
I made a very nice setup project (New Project -> Other -> Setup and Deployment -> Visual Studio Installer -> Setup Project), but I really like the way ClickOnce works.
Sadly I had to use a setup project because of some custom actions and registry editing during installation.
Is there a convenient way to make a ClickOnce deployment out of it?
You can't use any custom actions in ClickOnce and there is no way to edit the registry with ClickOnce.
If you need these features, ClickOnce will not work for you. There is no way to convert your deployment.
How do I publish a C++/CLI Windows Forms project for ClickOnce deployment? The properties window for C++/CLI projects does not include a "Publish" tab (like in the C# projects).
You can follow the guidelines for manually deploying a ClickOnce application on MSDN.
This relies on the Windows Software Development Kit and command line tools instead of Visual Studio to do your deployment.
Just another note with this - if you can, I'd recommend trying to migrate to /clr:pure if possible. If you're working with native code, this won't work, but if it's a pure windows forms app, it will make the deployment scenario simpler, since you'll have fewer issues in ClickOnce with CAS requirements.
You cannot ClickOnce deploy an exe written in unmanaged code. The standard approach is to create a managed code stub exe that would launch your actual application.
Here's a related question.