Standard: Issues with .NET Standard and Click Once

[JranZu]

Looking forward to this fix... Not so much implementing the workarounds ;) -- Any ETA? Soon, Summer 2018, etc?

[NArnott]

This doesn't appear to work. System.Runtime is still not getting deployed even after adding the extra target to my csproj.

System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. ---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

[JPhilC]

This work around does not not work. It just moves the problem along so that the application will publish and install but it then will not run. You get an invisible APPCRASH with the following Application Event log.

Application: ClickOnceIssueDemo.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException Exception Info: System.IO.FileNotFoundException at ClickOnceIssueDemo.App..cctor() Exception Info: System.TypeInitializationException at ClickOnceIssueDemo.App.Main()

In the hope that someone can help with this I have created a simple application and put it here:.

I have been unable to determine what file is missing. The Fusion Log Viewer does not show anything and attaching the debugger directly to the exe does not give show any additional information either. I am at a loss how to resolve this. I have wasted a day and a half on this already.

The sample application targets .NET 4.7 and shows a main window displaying the time. It uses a .NET Standard 2.0 class library to provide the time. If you clone the repository and open the solution in VS2017 it will run fine.

The application is based on a sample provided by Laurent Bugnion of Galasoft for another issue I had related to his newly released .NET Standard version of MVVMLight.

[UPDATE]
I have just tried updating the test application to target .NET 4.7.1 and it seems to have resolved the issue. I removed the work-around hack to project file and it still seems to work. Going to try the same approach on the real project with which I am having problems.

[UPDATE 2]
Upgrading to target ,NET Framework 4.7.1 seems to have solved the issue for me. There are still minor niggles getting it to include certain files but at least now I see which files are missing in the Fusion Log Viewer.

[cilerler]

@terrajobst it seems it did not fix the issue

I compared the output between OnceClick and Non-OnceClick and files below are missing on OnceClick one. And because of that I'm getting the error Could not load file or assembly 'System.Runtime, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.

Any workaround for that? Thanks in advance 🤗

System.Collections.Concurrent.dll
System.Collections.dll
System.ComponentModel.dll
System.ComponentModel.EventBasedAsync.dll
System.Diagnostics.Contracts.dll
System.Diagnostics.Debug.dll
System.Diagnostics.Tools.dll
System.Diagnostics.Tracing.dll
System.Dynamic.Runtime.dll
System.Globalization.dll
System.IO.Compression.dll
System.IO.dll
System.Linq.dll
System.Linq.Expressions.dll
System.Linq.Parallel.dll
System.Linq.Queryable.dll
System.Net.Http.dll
System.Net.Networklnformation.dll
System.Net.Primitives.dll
System.Net.Requests.dll
System.Net.WebHeaderCollection.dll
System.ObjectModel.dll
System.Reflection.dll
System.Reflection.Extensions.dll
System.Reflection.Primitives.dll
System.Resources.ResourceManager.dll
System.Runtime.dll
System.Runtime.Extensions.dll
System.Runtime.Handles.dll
System.Runtime.lnteropServices.dll
System.Runtime.Numencs.dll
System.Runtime.SerializationJson.dll
System.Runtime.Serialization.Primitives.dll
System.Runtime.Serialization.Xml.dll
System.Security.Principal.dll
System.Text.Encoding.dll
System.Text.Encoding.Extensions.dll
System.Text.RegularExpressions.dll
System.Threading.dll
System.Threading.Tasks.dll
System.Threading.Tasks.Parallel.dll
System.Threading.Timer.dll
System.Xml.ReaderWriter.dll
System.Xml.XDocument.dll
System.Xml.XmlSerializer.dll

_Update Upgrading to target ,NET Framework 4.7.1 seems to have solved the issue for me too. I removed the work-around from the project file and it still seems working_

[Shashanka77]

Actually we are still running into the issue with this ClickOnce deployment even after upgrading to 4.7.1.

[joperezr]

Yes, this workaround won't work when targeting 4.7.1. We are in contact with the ClickOnce team in order to get a fix for this issue.

[clairernovotny]

This also affects the Desktop Bridge WAP projects. The right files weren't getting copied into the AppX directory. Same list above.

[ikourfaln]

@terrajobst
regarding this issue, is there any update?!

[nzain]

I've tested the described workaround on a net462 WPF clickonce project published from VS2017 - did not work. The app crashes and my log says

---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. 
---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

when instantiating the first (main) viewmodel of the WPF application.

A few weeks ago we successfully published from VS2015 on net46 without any netstandard dependencies, of course. Unfortunately, we did not even see this issue during the upgrades, since it compiles and runs happily. Others have said, that upgrading to net471 might resolve the issue - gonna try now. However, I'm not sure if this is is acceptable, since there is no net471 installer for some windows 10 versions (we're behind company wsus).

[JPhilC]

At the moment I think your only option is to publish to a staging area, edit the config file to change the version range of the affected assemblies then save as and resign the manifest files using mageui. That is the way I am currently deploying with clickonce. Here are my notes as to what I do:

[nzain]

I can confirm that simply targeting net471 _would_ resolve my issue, but that does not work on all company machines, since 471 only installs on some very specific win10 versions not available on our wsus. We give up (restored last working net46 clickonce version without netstandard dependencies) and wait.

[NArnott]

net471 doesn't appear to solve my issue, and I'm also concerned that net471 is limited on the windows versions. We are now very much in a stuck situation. We need to use nuget packages that have dependencies (such as Microsoft.Extensions.Logging), which only has a netstandard1.1 version. Once we pull those kind of nugets into a WPF app that uses clickonce, our deploys fail.

Is there any work happening to fix this?

[kevingoos]

I am looking into the same deploy issue, and like @nzain said, upgrading to 4.7.1 will limit the windows versions. Hope there will be a fix soon?

[joperezr]

Yes, we are very sorry you are hitting these issues. We have identified the problem and have contacted the clickOnce team in order for them to fix this ASAP. The fix is on track to make it to VS 15.8.

[kevingoos]

@joperezr and is there any info about when this vs version will be released?

[Shashanka77]

Has anyone tried adding these dlls to the project as content ?

[kevingoos]

@Shashanka77 no not tried this yet, feel free to try!

[joperezr]

is there any info about when this vs version will be released?

I believe timelines for releases are not defined yet, but I'll try to find out and update this thread.

[NArnott]

@Shashanka77 I just tried the dlls as content files, as it seems to work. It seems that in general Click Once blacklists any assembly that matches one that exists in the .NET Framework, such as System.Runtime or System.IO. Assembly names like System.IO.Compression doesn't exist in the framework, so makes it into clickonce deployments by default.

Adding as content files (which I have about 10 that were needed) adds more management, such as when adding or upgrading nuget packages, but it works for now. Really looking forward to that fix.

Here's an example of the addition to my csproj file that forces their inclusion into a clickonce package:

<Content Include="..\packages\System.Diagnostics.Tracing.4.3.0\lib\net462\System.Diagnostics.Tracing.dll"> <Link>System.Diagnostics.Tracing.dll</Link> </Content>

[vrykov]

@joperezr are there any news about this issue? This is real pain for me

[clairernovotny]

@NArnott What if you use a glob? I had to do something similar, for similar reasons, for the WAP packaging project for Desktop Bridge apps. Adding the entire output directory of the app as content, with the right Link path, did the trick:

https://github.com/NuGetPackageExplorer/NuGetPackageExplorer/blob/afe915819a7411113c5043f53cfb3355cd66bf24/PackageExplorer.Package/PackageExplorer.Package.wapproj#L56-L58

<Content Include="..\PackageExplorer\bin\$(Configuration)\net461\**\*.dll">
    <Link>NuGetPackageExplorer\%(RecursiveDir)%(Filename)%(Extension)</Link>
</Content>

[NArnott]

@onovotny Thanks for the trick. I tried it, and started getting errors from clickonce that files were already installed. Looks like any assembly that is referenced both in the project as a dll, and as content (per your work-around), would end up in the click-once manifest twice, causing it to fail to download on a user machine. Any ideas how to solve that problem?

[clairernovotny]

You'd need a dedup step, or an exclude. depending on how many files are duplicated, it could be easiest to just have Exclude="..\foo\bar.dll;..\foo\zed.dll".

[clairernovotny]

If you can get the already referenced items as a set of items, then you can also do Exclude="@(TheItems)"

[bruno-david]

The details provided by @onovotny worked fine for me.
Waiting on the proper fix for this issue...

[DOMZE]

Can confirm that the workaround along with changing the target framework does not work, but including the file as content works.

[hafkenscheid]

I seem to have the same problem as @Shashanka77:

Unable to install or run the application. The application requires that assembly System.Xml.XPath.XDocument Version 4.1.0.0 be installed in the Global Assembly Cache (GAC) first.

As suggested by @onovotny, I tried including the dll as content in my csproj file:

  <ItemGroup>
    <Content Include="bin\Debug\System.Xml.XPath.XDocument.dll">
      <Link>System.Xml.XPath.XDocument.dll</Link>
    </Content>
  </ItemGroup>

However, the error remains...

[Karlheinzniebuhr]

Having the same issue, any updates or solutions yet?

[joperezr]

No updates on the fix, since we are still waiting for VS 15.8.

You can check the above comment from @onovotny which provided a possible workaround: https://github.com/dotnet/standard/issues/529#issuecomment-366695368

[RealDotNetDave]

This did not fix the issue for me either.

[NArnott]

I'm using version 15.6.6 now, and it seems to be working.

As a workaround, I had added the missing DLLs as content links in the csproj used for clickonce. After updating visual studio, I deployed and started getting the following error when I ran the program:

The file 'C:\Users*USERNAME\AppData\Local\Temp\Deployment\BZO7LWNL.LKQ\TWK6GYPB.WB8*SomeAssembly.dll' already exists.

I then looked at the manifest and noticed that the files I added manually were now getting added twice, so I removed the manual additions from the csproj, and it's correctly adding them now.

[nzain]

Using VS 15.6.6 too, but the problem persists for me. We build for

<framework targetVersion="4.6.2" profile="Full" supportedRuntime="4.0.30319" />

Starting the application shows the following error:

@NArnott maybe you now run a mix, where some files are copied correctly and some files are duplicated by yourself?

[raphil]

@nzain We are targeting version 4.7.1 and just did a ClickOnce deploy and got the exact same popup message as in your post.
Did you figure out any fixes?

[nzain]

@raphil As others have mentioned above, you can try to add missing dlls manually (Visual Studio: project properties > publish > application files). There are quite a lot dlls and I stopped trying after 5 or so. I'm waiting for the fix announced for version 15.8.

[kevingoos]

I am also waiting for 15.8 for 3 months now, is there no way to schedule this update in an earlier version?

Now I need to keep my nuget packages up to date in two version, the .net core version (for my asp.net core projects). And the .net framework 4.6.1 version (for my WPF projects). This is not a really big task but it is just annoying and double work. So it would be really handy if it get fixes somewhere soon :)

[raphil]

@nzain actually, I was able to address this by compiling on 15.5.6 instance I had. I will be sure not to upgrade that instance until we know all is working well. :)
Adding the dll's manually will not work, as you said, there are many and we would need to do this each time we publish (we publish using ClickOnce). (I guess I could always create a directory and place all the missing dll's and copy and paste each time, but.....)

[MelbourneDeveloper]

Me too.

[saulyt]

I too am having this issue. I see that 15.8 is now released in preview. Has anyone installed it to verify that this issue is fixed?

[arthurvb]

For our deployment it seems that installing the latest .net framework (4.7.2) on the client fixes the issue.

[saulyt]

@arthurvb Was it enough to install 4.7.2 on the deployment machine, or did you need to target 4.7.2 in your application?

[banksdev]

Upgrading to .NET 4.7.2 did not work for me sadly, however I have found that going into the Project Properties -> Publish, and clicking Application Files and then one by one setting the assemblies needed to Include instead of Prerequisite worked for me.

[arthurvb]

@saulyt only on the machine where the program is run

[saulyt]

I upgraded a machine to .NET 4.7.2 and did not have the missing file error during the clickonce installation, but the program crashed on startup with no error message (just disappeared and was no longer running.) I then installed VS 15.8 Preview and installed again on the 4.7.2 machine and it worked. However, when I tried installing it on a machine with 4.7.1 I once again received the missing files error during installation. It seems that VS 15.8 does not fix the issue (at least if you are not running .NET 4.7.2).

[JPhilC]

Just been looking at the fixed issues in VS 15.8 Preview 2 and this issue does not appear to be there. Can someone confirm whether a fix for this issue is scheduled for release with VS 15.8?

[joperezr]

As far as I can tell, unfortunately, ClickOnce team haven't yet been able to produce a fix for this issue. I'll push for somebody on their team to report back to this thread so that we can get an ETA and a state of things.

[kevingoos]

@joperezr any progress?

[joperezr]

I was able to get in touch with the ClickOnce team and they say the fix is still targeting 15.8. It just hasn't been on the Previews of 15.8 yet, but it should be there for RTM.

[RhomGit]

@joperezr Thanks for the update.

Its pretty disappointing this has taken so long to resolve (if indeed it even has been resolved).
https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-preview-relnotes#15.8_Preview3

[John-Hart]

As @joperezr mentioned, it will be included in 15.8, unfortunately we did just miss the deadline for Preview 3.

[kevingoos]

@John-Hart So if I understand it correctly, the fix is implemented at this point?
Sorry that we are so skeptical about this now, but we are already waiting for 6 months on a fix, which is crucial to start using .net standard, in a stable way, in our project...

[kevingoos]

I cannot find it in preview 4 either?

[Janidbest]

This was the issue with 15.5.6 target 4.7.1, after VS update to 15.7.5 today its got fixed with the work around specified on the top of this thread.

[cealmees]

@Janidbest Is really solved the issue? Today I started ClickOnce for a new production release which is scheduled for tomorrow. I guess we all lucky today!

[dj-curls]

Adding this to my csproj, after retargeting 4.7.1 doesn't work

<ItemGroup> <Content Include="..\PackageExplorer\bin\$(Configuration)\net461\**\*.dll"> <Link>NuGetPackageExplorer\%(RecursiveDir)%(Filename)%(Extension)</Link> </Content> </ItemGroup>

Also upgrading to .net 4.7.2 didn't work either. Really looking forward to this fix

[rholsman]

I was having this issue with a 4.7.1 WPF app, but went into the publish settings on the wpf projects properties and then under install mode and settings section clicked the application files button. Found the missing reference which for me was system.net.http.dll which had its publish status as Prerequisite and changed it to Include and this resolved the issue. I am running VS 15.7.5 and seem to be able to resolve the issue with this.

[clintmasden]

If you are publishing a WPF / WinForms Application you can go to your Project > Properties > Publish > Application Files > and change Publish Status ( Prerequisite (Auto) to Include). Original Source Stack Overflow Step by Step Process. If you are deploying a Class Library or VSTO addin that's where it becomes complex since you don't have "Publish > Application Files", in which you have to manually modify the Click Once Manifest to include the DLLs, Add the Deployed DLLs to the publish directory, and finally resign it the solution manifest and the application manifest with MageUI. I created an article that is also Step By Step here.

[RhomGit]

As @joperezr mentioned, it will be included in 15.8, unfortunately we did just miss the deadline for Preview 3.

Has anyone tested if the fix is any of the latest couple of 15.8 previews?
Visual Studio 2017 version 15.8 Preview 5 - released July 26, 2018

edit: I saw on this thread that the fix should be available now on the previews (since mid-July).
https://developercommunity.visualstudio.com/content/problem/111414/clickonce-with-dependcy-with-netstandard-does-not.html

[willson556]

Has anyone tested if the fix is any of the latest couple of 15.8 previews?
Visual Studio 2017 version 15.8 Preview 5 - released July 26, 2018

I successfully built a ClickOnce release today with no project edits and a target of .NET Framework 4.7.1 using 15.8 Preview 5.

[RealDotNetDave]

I am able to create a ClickOnce package now without any issues in VS2017. I still don't see .NET Core as a prerequisite. Will that be added?

[velvetdust]

We have this error _(Unable to install or run the application. The application requires that assembly System.Xml.XPath.XDocument Version 4.1.0.0 be installed in the Global Assembly Cache (GAC) first.)_ only for users with Windows x86. Users with Windows x64 can install and use ClickOnce app without errors

[Daniel-Svensson]

Is this fix intended to solve https://github.com/Microsoft/msbuild/issues/3057 and https://github.com/Microsoft/msbuild/issues/3058 ?

[noisycarlos]

Honestly, I'm not quite sure what I copy/pasted into my project, but it worked. Thanks!

In my case, I got an error on Installation that said something like "The application requires that assembly netfx.force.conflicts version 0.0.0.0"

[joperezr]

@RealDotNetDave

I still don't see .NET Core as a prerequisite. Will that be added?

.NET Core is not a prerequisite for your app to run. Your app will run on .NET Framework, and it only needs the right facades in place in order to work. With the fixes that the ClickOnce team made, these facades will be packaged as well, so it is not a requisite to have .NET Core.

[terrajobst]

Closing as this an announcement. For the record, we've started to track issues related to .NET Framework support with this label.