You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tool can run in both netcore and netframework because:
44
+
The tool can run in both netcore and netframework because:
45
45
- The conversion needs to be able run in a dot net core process so it works cross platform
46
46
- So linux users can convert dot net core projects
47
47
- The conversion needs to be able to run in a net framework process because:
@@ -50,4 +50,4 @@ The tool can run in both netcore and netframework
50
50
51
51
## Future
52
52
53
-
The package is about 27MB. The size is made up by the Roslyn dependencies. It includes most of Roslyn, but not MSBuild (which must be installed on the machine). In future we could get Roslyn from the installation too like the VS extension does. It just needs careful management of versions. The dot net framework version can match the vs extension dependency versions. The dot net core one can depend on later versions.
53
+
The package is about 27MB. The size is made up by the Roslyn dependencies. It includes most of Roslyn, but not MSBuild (which must be installed on the machine). In future we could get Roslyn from the installation too like the VS extension does. It just needs careful management of versions. The dot net framework version can match the vs extension dependency versions. The dot net core one can depend on later versions.
0 commit comments