In Visual Studio when you create a new Publishing Profile you can choose to Deploy the project as a ZIP package.
What does this do?
Why choose this over not deploying as a ZIPPED package?
Related
I have a WPF project in Visual Studio 2017 that correctly publishes if I go on the project properties and publish it from there it does so just the way I want, but when I run msbuild /target:publish it creates an unwanted .exe file.
Furthermore, there's another option I enabled on Visual Studio which is in the Deployment tab called "deployment web page", which I just put "clickonce.htm".
So, when I publish using Visual Studio I get these files:
Application Files
clickonce.htm
[ProjectName].application
setup.exe
And when I use MSBuild:
Application Files
[ProjectName].application
[ProjectName].exe
setup.exe
How can I make it so that MSBuild outputs the same as Visual Studio?
I am trying to publish a .csproj through the TFS Visual Studio Build task. When I Publish this project manually through Visual Studio 2017 it publishes correctly and everything works.
However we I run the build definition through tfs I am getting the following error:
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Professional\MSBuild\15.0\Bin\amd64\Microsoft.Common.CurrentVersion.targets
(1656, 5) C:\Program Files (x86)\Microsoft Visual
Studio\2017\Professional\MSBuild\15.0\Bin\amd64\Microsoft.Common.CurrentVersion.targets(1656,5):
Error : Project '..\STARS.Web\STARS.Web.csproj' targets 'net471'. It
cannot be referenced by a project that targets
'.NETStandard,Version=v2.0'.
What am I doing differently between the TFS Build Task and publishing manually through Visual Studio 2017. Is there any way to check the steps both these process are doing? Both use the same publish profile.
TFS Build Definition Task:
I have built a custom menu command (Launch Application1) using Visual studio SDK-13(using C# extensibility) which pops up in the 'Tools' menu of Visual studio.
Now, when I run this project a new instance of Visual studio opens up and 'Launch Application1' is shown under the 'Tools' menu of that visual studio.
The output is a '.dll' file and not an '.exe' but I want to have an installer for this, so that a simple installation can deploy this into any visual studio environment permanently. Please help!
The output of a visual studio extension - in your case a custom menu command is always a dll file, with the dll file visual studio also creates a VSIX file which is a Zip file and contains the dll and some other manifest files.
The VSIX file can directly be distributed for installation on other systems, If the correct version visual studio is installed, the extension will be installed with that.
For basic stuff you can use the VSIX as your redistributable. If you want to have a proper MSI file you can try WiX installer.
I have found loads of refernces to creating a simple setup.exe file in VS by doing the new project - setup wizzard but there is only Enable InstallShield Limited Edition.
I can't install the following for VS 2015, it thinks VS is not installed:
https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d
Any advise? I don't want all of the folders and files that come with publishing my application, only setup.exe
Thanks
No other option available for my needs.
Had to uninstall VS 2015 and install VS 2013 to be able to use InstallSheild.
Follow these instructions provided by #Ken White
Creating a setup.exe in InstallShield in Visual Studio
We are using Visual Studio 2008 and .Net 3.5. we can build our C# projects in build machine by using MSBuild from SDK because we don't have visual studio installed on the build machine.
Now we are trying to build the Setup project with similar settings. It looks like the MSBuild doesn't like .vDProj. any idea how can we do that?
thanks,
EDIT:
the build machine only has SDK installed, no Visual Studio installed, no other thirdparty build tool installed.
Install Visual Studio on the Build machine.