question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failing to compile in VS 2017

See original GitHub issue

When using C# 4.6 +

Severity Code Description Project File Line Suppression State Error The “DllExportAppDomainIsolatedTask” task failed unexpectedly. System.ArgumentException: Requested value ‘Version46’ was not found.

Server stack trace: at System.Enum.EnumResult.SetFailure(ParseFailureKind failure, String failureMessageID, Object failureMessageFormatArgument) at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult) at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase) at RGiesecke.DllExport.MSBuild.ExportTaskImplementation1.<>c__DisplayClass126_0.<GetGetToolPathInternal>b__1(Version version, String toolName) in D:\prg\projects\DllExport\DllExport\RGiesecke.DllExport.MSBuild\RGiesecke.DllExport.MSBuild\ExportTaskImplementation.cs:line 608 at RGiesecke.DllExport.MSBuild.ExportTaskImplementation1.TryToGetToolDirForFxVersion(String toolFileName, Func3 getToolPath, String& toolDirectory) in D:\prg\projects\DllExport\DllExport\RGiesecke.DllExport.MSBuild\RGiesecke.DllExport.MSBuild\ExportTaskImplementation.cs:line 775 at RGiesecke.DllExport.MSBuild.ExportTaskImplementation1.ValidateToolPath(String toolFileName, String currentValue, Func3 getToolPath, String& foundPath) in D:\prg\projects\DllExport\DllExport\RGiesecke.DllExport.MSBuild\RGiesecke.DllExport.MSBuild\ExportTaskImplementation.cs:line 756 at RGiesecke.DllExport.MSBuild.ExportTaskImplementation1.ValidateFrameworkPath() in D:\prg\projects\DllExport\DllExport\RGiesecke.DllExport.MSBuild\RGiesecke.DllExport.MSBuild\ExportTaskImplementation.cs:line 722 at RGiesecke.DllExport.MSBuild.ExportTaskImplementation1.ValidateInputValues() in D:\prg\projects\DllExport\DllExport\RGiesecke.DllExport.MSBuild\RGiesecke.DllExport.MSBuild\ExportTaskImplementation.cs:line 507 at RGiesecke.DllExport.MSBuild.ExportTaskImplementation1.Execute() in D:\prg\projects\DllExport\DllExport\RGiesecke.DllExport.MSBuild\RGiesecke.DllExport.MSBuild\ExportTaskImplementation.cs:line 410 at RGiesecke.DllExport.MSBuild.DllExportAppDomainIsolatedTask.Execute() in D:\prg\projects\DllExport\DllExport\RGiesecke.DllExport.MSBuild\RGiesecke.DllExport.MSBuild\DllExportAppDomainIsolatedTask.cs:line 397 at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.Build.Framework.ITask.Execute() at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext() TestDll

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:14 (8 by maintainers)

github_iconTop GitHub Comments

5reactions
3Fcommented, Mar 14, 2017

hmm, I see

temporarily:

try to install msbuild tools (~20 MB), for example:

or try to reduce version via DllExportTargetFrameworkVersion:

<DllExportTargetFrameworkVersion>v4.0</DllExportTargetFrameworkVersion> <!-- for dllexport -->
<TargetFrameworkVersion>v4.6.2</TargetFrameworkVersion> <!-- for your project -->

upd. related:

1reaction
3Fcommented, Mar 13, 2017

This problem should be fixed in v1.5.2 Public release v1.5.2.22710 [ 1f6b2d9 ]

Read more comments on GitHub >

github_iconTop Results From Across the Web

Visual Sdudio 2017 Professional failed to build but no errors
My Visual Studio 2017 Professional failed to build any solution/project even a newly created template project for example a simple console ...
Read more >
MSBuild fails to compile but passes on Visual Studios 2017
Using the new MSBuild in the build tools path (C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSbuild.exe), I ...
Read more >
#include throws compile error in VS 2017. - ...
It works fine at VS2015 but it will throw the following errors on VS2017 (V15.7.4). Any idea? 4>c:\program files (x86)\microsoft visual studio\ ...
Read more >
Failed build on Windows using VS2015 (with VS2017 also ...
My experience is that you end up corrupting visual studio configuration of you install them out of order (install older version after installing ......
Read more >
Fixing Visual Studio Intellisense Errors - Rick Strahl's Web Log
The actual build of the code succeeds, but Intellisense is flagging several classes as missing even though they clearly exist and clearly ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found