Fix build and pack as .NET tool - #2
Conversation
- Adjust target frameworks. - Migrate current projects to 4.7.2, add also to target framework in projects referencing these. - Rework referencing projects to get proper referencing. - Fix output type of TFConvert to output executable. - Add hack to allow package as .NET tool despite being able to run only on windows. - Add check for running on Windows platform. - Move properties to package as tool to main project. - Assembly name, package id and tool command name are now all lower case and the same for consistency.
51a59b8 to
1860cd3
Compare
|
This gives me
Can you comment on commenting out some of the tests? |
|
Yes, I can see the same here when trying to install... will try some workarounds in the coming days |
|
This is defenitly not working at all! I'm thinking that another approach could be to have the CLI build as a .NET tool, but instead of TFConvert being the tool it would be instead a wrapper that would call the "original" TFConvert CLI that can be build as usual (just that updated to the latest .NET Framework version). |
Uh oh!
There was an error while loading. Please reload this page.