What better way to try out VS2017 RC, by creating a .Net Core solution on windows, and building it on linux.<\/p>\n
However the standard .Net core installation guide for Linux<\/a>, as of the date of this post, will not build VS2017 RC projects, due to it utilising *.csproj files, and no longer creating xproj \/ project.json files.<\/p>\n Expect an error along the lines of:<\/p>\n A version check will show that the \"latest\" is quite on the bleeding edge as it needs to be.<\/p>\n Compare this to Powershell after a VS2017 .Net Core install in the windows box.<\/p>\n Initially, the only option looked to be building from the preview branch in git.<\/a><\/p>\n However, there is a series of preview binaries available for those looking to hit the ground running faster.<\/p>\n https:\/\/github.com\/dotnet\/core\/blob\/master\/release-notes\/preview3-download.md<\/a><\/p>\n Howover, that is waye tyopo easy.<\/p>\n Let's build us the .Net CLI.<\/p>\n After a git clone, switch to the preview 3 branch.<\/p>\n Initally, it's going to take a while, the bash that kicks it all off is \/build.sh<\/p>\n The scripts go three to four deep ,at least. Adding a set -x to the top level script next to the existing set -e will give us some visibility into how the build is going.<\/p>\n Once built set up a new symlink. As it will be to the same executable, dotnet, create it in a subfolder to \/user\/local\/bin, and then remove it, and remove the folder.<\/p>\n You can then have a stable binary, and a build version running side by side.<\/p>\n One nasty looking error I bumped into was this one, in red, making it extra ominous.<\/p>\n Let see, its mention Net 4.0, and a GAC< on a LInux bo-x that is running .Net Core.<\/p>\n Not looking good. There are no .Net 4.0 References in the project and the whole point of .Net Core is to stand alone with a dependency on Mono. As for the GAC reference, this message doesn't give is much to go on.<\/p>\n Until you realise all you need to do is restore the project.<\/p>\n It does show that while the base cross-platform functionality is there, removing the legacy windows reference is going to be some time away for this fledgeling framework.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" VS2017RC Tooling on Linux What better way to try out VS2017 RC, by creating a .Net Core solution on windows, and building it on linux. However the standard .Net core installation guide for Linux, as of the date of this post, will not build VS2017 RC projects, due to it utilising *.csproj files, and no longer creating ...continue reading [user@localhost]$ dotnet run\nThe current project is not valid because of the following errors:\n\/home\/user\/DotNetCoreASP(1,0): error DOTNET1017: Project file does not exist '\/home\/user\/DotNetCoreASP\/project.json'.\n<\/pre>\n
[user@localhost \/opt\/dotnet]$ dotnet --version\n1.0.0-preview2-1-003177\n<\/pre>\n
PS C:\\> dotnet --version\n1.0.0-preview3-004056<\/pre>\n
Building the .Net CLI in Linux<\/h4>\n
git checkout -b re1\/1.0.0.0-preview3\n<\/pre>\n
#!\/usr\/bin\/env bash\n#\n# Copyright (c) .NET Foundation and contributors. All rights reserved.\n# Licensed under the MIT license. See LICENSE file in the project root for full license information.\n#\n\n# Set OFFLINE environment variable to build offline\n\nset -e\n# Enable recursive debugging for verbose output\nset -x\n\nSOURCE=\"${BASH_SOURCE[0]}\"\n...<\/pre>\nPost Build<\/h4>\n
sudo mkdir \/usr\/local\/bin\/dotnet-preview3-dir\nsudo ln -s \/home\/user\/dev\/cli\/artifacts\/centos.7-x64\/stage2\/dotnet \/usr\/local\/bin\/dotnet-preview3-dir\nsudo mv \/usr\/local\/bin\/dotnet-preview3-dir\/dotnet \/usr\/local\/bin\/dotnet-preview3\nsudo rm \/usr\/local\/bin\/dotnet-preview3-dir -r<\/pre>\n
Troubleshooting<\/h3>\n
$ dotnet run\n\/opt\/dotnet\/sdk\/1.0.0-preview3-004056\/Microsoft.Common.CurrentVersion.targets(1107,5): error MSB3644: The reference assemblies for framework \".NETFramework,Version=v4.0\" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend. [\/home\/user\/DotNetCore\/hwapp\/hwapp.csproj]\n\nThe build failed. Please fix the build errors and run again.<\/pre>\n
dotnet restore<\/pre>\n