Closed MuminKhan closed 6 years ago
As with the reference issue, I am unable to duplicate this. Can you supply an example that does?
Sorry it took so long. Removing the Windows Script Host Object Model (IWshRuntimeLibrary) reference resolves the issue. Re-adding it causes it to break again.
Sorry, but as with the last time, the sample project works for me. There is more likely than not a difference in the set of SDKs or perhaps tool paths that is causing it to not be able to find AxImp.exe. The error message gives some detailed information about causes and potential solutions so that's the place to start.
You say that removing the reference gets it work work. If that's the case, you an probably just reference the assembly and XML comments file as the documenation sources rather than the solution. In that case it wouldn't look for the reference either and thus should build. If it does fail due to a missing reference exception, you can use the Assembly Binding Redirection plug-in to ignore it.
If you have a reference to IWshRuntimeLibrary in your project, MSBuild bombs out. This is similar to #397
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">