New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.NET 3.0 Preview (3.0.100-preview-009812) on Visual Studio 2019 Preview image #2762

Closed
FeodorFitsner opened this Issue Dec 10, 2018 · 14 comments

Comments

Projects
None yet
4 participants
@FeodorFitsner
Copy link
Member

FeodorFitsner commented Dec 10, 2018

@FeodorFitsner FeodorFitsner changed the title .NET 3.0 Preview on Visual Studio 2019 Preview image .NET 3.0 Preview (3.0.100-preview-009812) on Visual Studio 2019 Preview image Dec 10, 2018

@AraHaan

This comment has been minimized.

Copy link

AraHaan commented Dec 14, 2018

This commit will fail for me, is this only for the vspreview image or also for the stable ones as an opt-in as well? I would like to be able to use it on stable if my global.json asks for it on the build.
Elskom/ReleasePackaging@3086340

the failing build: https://ci.appveyor.com/project/Elskom/releasepackaging/builds/21002033

Currently most of my nuget packages are using stable instead of the preview images because it is currently a big wait for the preview image to start. Why does the stable image takes less time to start instead of the same time for both?

@FeodorFitsner

This comment has been minimized.

Copy link
Member

FeodorFitsner commented Dec 14, 2018

No, .NET 3.0 Preview is installed on Visual Studio 2019 Preview image.

@VladislavAntonyuk

This comment has been minimized.

Copy link

VladislavAntonyuk commented Dec 14, 2018

@FeodorFitsner , I have just tried to build the project with 2019Preview image, but msbuild was 15.9 and sdk was 2.2.100.
When it will be fixed?

https://ci.appveyor.com/project/VladislavAntonyuk/circlepacking/builds/21009402

@FeodorFitsner

This comment has been minimized.

@VladislavAntonyuk

This comment has been minimized.

Copy link

VladislavAntonyuk commented Dec 14, 2018

@FeodorFitsner

This comment has been minimized.

Copy link
Member

FeodorFitsner commented Dec 14, 2018

Use global.json to pin the version of SDK as suggested.

@AraHaan

This comment has been minimized.

Copy link

AraHaan commented Dec 14, 2018

https://ci.appveyor.com/api/buildjobs/26sewik7k6monkwn/log
nice, I would like to avoid the global.json though.

@FeodorFitsner

This comment has been minimized.

Copy link
Member

FeodorFitsner commented Dec 14, 2018

If you work through dotnet CLI instead of msbuild then the latest .NET Core will be used.

@VladislavAntonyuk

This comment has been minimized.

Copy link

VladislavAntonyuk commented Dec 14, 2018

But msbuild version should be 16.0 but it is 15.9

@FeodorFitsner

This comment has been minimized.

Copy link
Member

FeodorFitsner commented Dec 14, 2018

That's true. MSBuild path wasn't changed on VS 2019 image. What's its location btw?

@AraHaan

This comment has been minimized.

Copy link

AraHaan commented Dec 14, 2018

@FeodorFitsner but the problem is that your build system defaults to msbuild instead of telling it to instead do "dotnet build" when it detects a dotnet sdk style project on the Visual Studio images.

@VladislavAntonyuk

This comment has been minimized.

Copy link

VladislavAntonyuk commented Dec 14, 2018

C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin

@VladislavAntonyuk

This comment has been minimized.

Copy link

VladislavAntonyuk commented Dec 15, 2018

From Microsoft
MSBuild
The MSBuild toolset version has been changed from 15.0 to Current. MSBuild.exe is now in %VSINSTALLDIR%\MSBuild\Current\Bin\MSBuild.exe.
MSBuild (and Visual Studio) now targets .NET Framework 4.7.2. If you wish to use new MSBuild API features, your assembly must also upgrade, but existing code will continue to work.

@IlyaFinkelshteyn

This comment has been minimized.

Copy link
Member

IlyaFinkelshteyn commented Dec 17, 2018

Path to msbuild issue is tracked at #2776.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment