dresel/automaty

Automaty is a .NET Core based code automation tool for .NET Core projects.

automaty's Issues

Is GetProjectReferences broken?

I've tried to use Automaty to replace Scripty, but it fails to load project references. The referenced assembly is loaded from bin/Debug/Assembly.dll, but it's in fact located in bin/Debug/net451/Assembly.dll.

Remove Automaty.Common dependency from MSBuild task

I need to use the MSBuild task, but I don't want to reference Automaty.Common library.

Executing generator in multi-targeting project

Execution of generators fails with NullReferenceException in multi-targeting projects. It crashes somewhere in GetRuntimeLibraries method.

Tests / Usage with MSBuild 15.6.4+ installed throws MSB0001: Internal MSBuild Error: Missing resource '' error

Trying to run tests from the Automaty repository or actually using Automaty in a project with the --project switch causes the above error.

Research points to there being a mismatch with the version of msbuild being used vs the version referenced in the project. Unfortunatley I havnt had the resources to solve this issue, but am posting here so if anyone else experiences this issue they at least have an idea that the environment with VS2017 15.6+ is a contributing factor.

Some relevant pages:
https://developercommunity.visualstudio.com/content/problem/209174/vs2017-1560-msb0001-error-on-loading-net-core-proj.html

https://www.bountysource.com/issues/55876003-msbuild-errors-when-generating-metadata-for-sdk-based-net461-project-and-vs-2017-15-6

https://developercommunity.visualstudio.com/content/problem/209642/msb0001-internal-msbuild-error-missing-resource.html

Compilation results in "Invalid static method invocation syntax: "[MSBuild]::IsRunningFromVisualStudio()"

This is due to a change in MSBuild.

Please see below issue for solution and update all msbuild references to use new package

dotnet/msbuild#2775

Files generated with MsBuild task are not part of compilation

I suppose it's because the MsBuild target runs before CoreCompile but it should probably run before BeforeBuild.