I have a ClickOnce application that I would like to deploy to a SharePoint location. I have included the path to the SharePoint location on my local machine as the Publishing Folder Location ("C:\Users%username%..."). However, I am unclear as to Installation Folder URL that I can use for this deployment? Is this the web URL for the same folder on the online version of SharePoint (\xxxxxx.sharepoint.com...)?
This is the complete process for publishing to a shared folder.
Publish using ClickOnce and deploy using SharePoint.
Add a Document Library.
Create a new folder.
Select (Actions > Open with Explorer).
Copy the URL into the following folders:
Publishing Folder Location - \website.com\sites\name\folder
Installation Folder URL - website.com/sites/name/folder/
Click Prerequisities and untick "Create setup program in install prerequisite components"
Select (Build > Publish)
This should create a file at the top level (extension .vsto)
and a subfolder called "Application Files"
Related
I have a ClickOnce application sitting on my company's file server, including the setup.exe and the .application manifest. Due to network settings, users that wish to install my application must copy the setup.exe to their local machine. Unfortunately, the installation fails if it can't find the manifest. We can get around this by copying the manifest to the local machine alongside the setup.exe. The manifest has the "deployment location" set as the file server, so the copied local manifest is never used; it's only purpose is to placate the installer.
Is there a way to tell the installer to look for the application manifest at the specific file server location, and not look for it in the same folder as the setup.exe?
I am trying to set up continuous integration on my server using Visual Studio online.
Created a new agent pool.
Installed and configured a new build agent that I added to that agent pool.
Then I trigger a new build of my code to be handled in my agent pool.
I manage to build it but how to set up the task "Copy and publish build artifacts".
My goal here is to just copy the final website files e.g. binaries, images, cshtml, but NOT all files such c# files. Well sort of like the "Right-click > publish" operation in visual studio.
What value do I need to enter in "Copy root" field? (please see image below)
The documentation is located at: https://msdn.microsoft.com/en-us/Library/vs/alm/Build/scripts/variables
It all boils down to what the output path for your binaries is. If you're not overriding it via an MSBuild argument, $(Build.SourcesDirectory) with a value of **\bin\* will probably get you what you're after.
For a web application, make sure you're building with appropriate MSbuild arguments (something along the lines of /p:OutDir=$(build.stagingDirectory) /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true should do the trick). This will get you a _PublishedWebsites folder in $(Build.StagingDirectory).
Then all you need to do is publish Copy Root of $(Build.StagingDirectory) and Contents of **\_PublishedWebsites\*
Keep in mind that Publish Build Artifacts means publish build artifacts to VSTS or a file share, not deploy build artifacts to a web server
Using ClickOnce, is it possible to include a file (resource, dll, image, whatever) to be copied to a different location and NOT the app folder?
What I am trying to achieve exactly is to install Microsoft.Web.Publishing.Tasks.dll + Microsoft.Web.XmlTransform.dll and their .targets to C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web so those msbuild tasks can be used on workstations that do not have Visual Studio installed.
It was so easy using a Setup Project before VS 2013!!
I repeat: I do NOT want those files to be installed in the app folder (so please don't tell me to set the option Copy to Output = Always" on project files).
Thanks.
No. You can't do it with ClickOnce.
Either deploy the files and write code to copy files when your app starts. Or use some other deployment option, like msi.
I have added an Xml configuration file to a web project in VS2008 using the “Add as Link” option on the “Add Existing Item” dialog. The Xml file is common to a number of other web projects within the solution so it exists in the Solution level directory. I have used the file link functionality to avoid a unique copy being added to each web project.
SolutionFolder
SharedConfigSettings.config
WebProject1Folder
WebProject2Folder
Problem
The problem is that the linked file is not deployed. I need the file to be copied to the root of the web application so that it is in the same location as the web.config file.
I have tried
1) Setting the file properties on the link as...
Build Action: Content
Copy to Output Directory: Do not copy
...results in the file not being copied at all
2) Setting the file properties on the link as...
Build Action: Content
Copy to Output Directory: Copy always
...results in the file being copied to the Bin directory below the web application root.
3) Post build event to copy the file. This works but is messy to implement because it requires additional steps to get this to work on the build server.
Is there a way that this can be done using the standard options available in the project file?
My application consist of an executable project and a dll library. My executable project has added the reference to the library project.
The library project contains some "content" files like .ini .bmp. The problem is that these files are not copied to the device when I deploy the executable project. Only dll file is copied. The curious thing is that all files are copied to the \ExecutableProject\bin\Debug directory on the desktop machine.
To workaround this I've set the deployment path of dll project the same as executable project and I'm deploying them both, but this solution doesn't seem to be nice.
I'm using VS2008 and my device works on Windows CE.
There are a few things to check.
Double check that the "Build Action" is set to "Content"
Make sure that the "Copy to Output folder" is set to "Copy Always" or "Copy If Newer"
Make sure that the deployment folder for the library project is what you expect (Properties->Devices->Output File Folder)
Make sure that the library project is set to the same target device as the executable
Make sure the library project is set to deploy for your configuration (Build->Configuration Manager)
Remember that if the content files are in a subfolder in the project, they will end up in a subfolder on the device