ExtensionTasksPath is now hard coded and cannot be overriden

mikefourie-zz / MSBuildExtensionPack

MIT License

366 stars 104 forks source link

ExtensionTasksPath is now hard coded and cannot be overriden #56

Closed djjay0131 closed 7 years ago

djjay0131 commented 8 years ago

You are now assuming that all of the tasks will live in the tools/net40 folder in the packages folder. My application actually packages the files up for use in a deployment step later and that means I can't custom set up my files. Can you change it back so that you can override the variable ?

mikefourie-zz commented 8 years ago

Could you elaborate? When did I hardcode it?