search

mikefourie-zz / MSBuildExtensionPack

MIT License
366 stars 104 forks source link

Hard-coded install path in MSBuild.ExtensionPack.tasks broken by different install path #82

Closed RobCoder closed 5 years ago

RobCoder commented 6 years ago

Seems like the install path got changed recently, which breaks existing import statements. This would not be a big deal, since the installer allows the user to specify a different install path, but unfortunately the default install path is also hard-coded into MSBuild.ExtensionPack.tasks. If a different install path is selected in the installer (such as the previous MSBuild/ExtensionPack), it results in MSBuild being unable to find the assemblies that implement the tasks, because the paths in MSBuild.ExtensionPack.tasks are wrong.

Not sure the best way to fix it. An env var added by the installer to indicate the install path would work.

mikefourie-zz commented 5 years ago

you could specify an environment variable called ExtensionTasksPath and that will override anything in the provided .tasks file if you install to a different location.