I have a winforms application that had click once working in visual studio. after the recent update to 16.11.5, the exact same publish profile for the clickonce app is no longer working after updating from an earlier version of visual studio.
Anywhere I should check for changes to click once? this is really baffeling and my google skills seem to be failing me in finding an issue.
The only output I get from the publish (build output log) is that the publish succeeded. The files are being published to the staging publish folder and I have made sure I have full permissions on the network share configured for the user install location.
So I've created an offline installed of VS 2017 Community on my laptop using this command:
vs_community.exe --layout "D:\Downloads\VS Community 2017" --lang en-US --add Microsoft.VisualStudio.Component.CoreEditor Component.WebSocket Microsoft.VisualStudio.Workload.ManagedDesktop Microsoft.VisualStudio.Workload.NetCrossPlat Microsoft.VisualStudio.Workload.NetCoreTools Microsoft.VisualStudio.Workload.Node Microsoft.VisualStudio.Component.TypeScript.2.0
When I transfer the setup files onto my corporate PC (which is behind a firewall) and run the "vs_community.exe" setup file, all I get is this error. There's no way to bypass the corporate firewall or to make exceptions. How do I install VS 2017 offline? Am I missing something here?
Edit: I have installed VS 2017 on my laptop keeping the internet connection active. Then when I disconnect the internet on my laptop and try installing again, the installer launches! So perhaps there are some dependencies missing on my corporate PC that are now installed on my laptop?
Edit: The above command installs .NET, .NET core, Xamarin, Node.js, TypeScript and C++ for Mobile. The total downloaded size is 13.2 GB.
It worked!! All I had to do was install the certificates into the root CA! Something I missed noticing in the VS 2017 docs:
How to install from the offline installation folder
Install the certificates (They are in the "certificates" folder, which is in your Layout folder. )
Simply right-click each one and choose Install PFX.
Specify Local machine (not current user)
You can use an empty password
Run the installation file. For example, run:
c:\vs2017offline\vs_enterprise.exe
--- Microsoft Docs
Edit: Remember to install the certs using the Admin account on the PC, or it won't work...
Please try to follow this steps:
Right click on exe file.
Select "Properties".
Click on the "Digital Signatures" tab. Now you can see "signature list".
Select signature
Click on "Details" button.
Click on "View certificate" button
Click on "Install certificate" and follows installation wizard
All certificates within "signature list" should be installed. I use Windows 10.
Was doing this for VS Community 2017 and it would install everything and it does the core installation without any trouble. However, if i select to install the universal or .Net development portions it will install it almost completely, but it will fail on two files. It will say that it cannot download the files from the internet. The files exist in the installation directory and I even went and downloaded the files and placed them into the appropriate directories and it still thinks that it needs to download those two files preventing me from completing the installation process. If I just continue it will install everything else except those two files. I've tried this with a few different layout downloads in different forms (ISO, directory, etc) and same issue (so it isn't a bad download or anything, and I'm sure I did that all correctly). The two files are:
https://download.visualstudio.microsoft.com/download/pr/10983757/f8c877406947fdc71ed2dd9127d2f9fa/microsoft.codeanalysis.visualstudio.interactivecomponents.resources.vsix
https://download.visualstudio.microsoft.com/download/pr/11347028/25bedee219940beceecab91dac231235/microsoft.visualstudio.testtools.testplatform.legacy.core.resources.vsix
If I plug myself online and do a repair it will go grab those two files without having to grab everything else, but it kind of defeats the purpose. Don't expect a solution, but wanted to mention it because all the other problems are related to installing the certs and I can't find anything online about it failing on just a few files.
In my case it was related to CNG key isolation windows service, it was disabled, the solution mentioned in below link:
Visual Studio 2017 - Can't install
How i solved mine.
I downloaded the setup helper from Microsoft website (i downloaded the enterprise installer, because that's the offline installer version i have )
I ran the program, and it wanted to download the complete setup, so i cancelled it
I ran my offline installer (vs_Enterprise.exe)
Then it fixed the issue.
I disconnected the internet, and continued with the offline installation
I have the same issue after uninstalling SSDT for Visual studio 2017, Can't remove and reinstall or update visual studio 2017.
I just restart my machine and it's OK.
my be you have also to log in as an administrator ( it depends on your machine configuration and what you can do with you current account)
Edited to avoid misunderstand
Running the downloaded Visual Studio layout as administrator worked for me.
Maybe the VS_Version.exe try to normally download the files because it can't access to files in the layout (sometimes named backup), like me, in my job we have a lot of restrictions and when I ran the VS_version.exe tried to download and get the message error, but when I ran again the .exe as Administrator the installer started normaly, getting the files from the backup folder
I'm developing a Windows app in Visual Studio 2013. When I use the publish feature, it creates a setup to install the app.
I don't want it to create a setup. I want it to build and deploy into a test environment, ready to be executed, without overwriting that environment's app.config. It would be great if I could configure multiple environments and choose which to be deployed.
I found https://msdn.microsoft.com/en-us/library/hh191495%28v=vs.120%29.aspx but it requires TFS. I wanna do it directly in VS.
To make it more clear, the best solution would me to type F6 - or any other shortcut - and have Visual Studio do the following:
build solution
copy exe and dlls to a specified folder
don't change destination's app.config
if possible, copy also source code so that debugger when opened is able to run thru it
It should be able to configure multiple profiles, so that it can send files to multiple test environments.
I got my app successfully published, ran the setup.exe just fine, but it lloks like the app was installed in an odd place, buried way down deep:
C:\Users\sndevfarmsvc\AppData\Local\Apps\2.0\HQ0721DB.Z4Q\8TDK6PMR.A39
Is this normal? In the publish section of the project in VS 2010 there is a place for installation folder, but that requires a URL....what if I want it always to install to c:\program files\ on whatever machine it is run on?
thanks,
Phil J.
Yes that's normal for a ClickOnce application.
The installation folder is the location where there application is installed from.
If you want to install into a different location you'll have to use a different installation program.
I've seen popping up around the web recently .application files, for .NET installations. (Application manifests, per the extension details).
How exactly does one create these .application files in Visual Studio, and how do they differ from a standard windows setup? Please enlighten me.
I'm a C# developer, but never used a .application installer before.
How exactly does one create these .application files in Visual Studio?
.application file is automatically created when you do a click-once deployment.
For click-once deployment, you can
Right click on the project you want to release and choose publish menu item.
-- or --
Right click on the project, select properties, go to publish tab to publish.
how do they differ from a standard windows setup?
You would create a standard windows setup program by creating a setup project in your solution. And also they differ in a way that, for click-once, end-user does not have to install the program on their local machine.
You can learn more about differences between them from MSDN
Choosing Between ClickOnce and Windows Installer