5 ms·
Yes, Really, and I am sure there are some people who have had no problems. That doesn't invalidate the countless hours I spent making this dreadful system work.
by DSteinmann 10y ago
Yes, Really, and I am sure there are some people who have had no problems. That doesn't invalidate the countless hours I spent making this dreadful system work. Did you put it on your build server without installing Visual Studio on it?
- colemickens 10y ago>Did you put it on your build server without installing Visual Studio on it? Huh? `docker run microsoft/dotnet`. Took about 2 seconds to get it running on my Jenkins build server. In reality, it took literally no effort. My entire full stack app requires `make` and `docker` to build and nothing else. The backend is an AspNetCore API.
- dsp1234 10y agoOur build server (TeamCity) does not have VS installed. I can actually tell you the exact software installed on the build server: 1.) Window Server 2016 (Base OS) 2.) SQL Server 2016 Express with LocalDB only (used for longer integration tests that need to validate migrations) 3.) DotNetCore.1.0.1-SDK.1.0.0.Preview2-003133-x64.exe (.NET core SDK 1.0.1 download from https://www.microsoft.com/net/download) 4.) BuildTools_Full.exe ("Microsoft Build Tools 2015 Update 3" https://www.visualstudio.com/downloads/#d-build-tools). If you have this, then you don't need the full VS install 5.) NodeJs (for running webpack as part of 'dotnet publish') 6.) TeamCity and Octopus Deploy agents That's it.