Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
MSbuild makes me want to blow my brains out.
I know it's no longer used in .NET Core and all the lucky people that don't have to deal with .NET Framework can happily move on.
But here I am, a complete idiot. Expecting MSBuild to build the exact same way from the CLI as it does if I run a build in Visual Studio. Expecting the build server to consistently produce the same result as if I built my solution locally.
Demanding meaningful earnings and error messages that don't leave me completely perplexed as to what's actually going on in the compiler.
Fuck me and fuck .NET Framework. Thank you for coming to my TED talk.8 -
Fuck .NET and vsbuildtools
For days i've been trying to build a project on a build server without installing visual studio but this seems impossible.. the build tools dont install the required dlls and even after adding those manually from a dev Machine msbulld fails.
Fuck this3 -
Guys, please be mindful of your dependencies. I just ran "npm install" and whole hell broke loose.
Imagine having to install 3.6GB of VS2017 C++ junk, just to make the damn node-sass compile.
Obviously the module needs to build on my machine, but one would expect that a nodejs module would not depend on msbuild. Funny how nature does that... -
Huh, just created a job in Jenkins to run msbuild over some solutions. The job accepted a parameter called "Configuration" which was just some simple JSON.
Everytime I ran the job, msbuild failed.
Then I realised that the Debug/Release info for a .NET Solution gets put into an environment variable called "Configuration" that msbuild creates and relies on! >.< -
> Be me
> Get exhausted with Rusts borrow checker while making games and decide to switch to another language
> C# looked good, I just made a mod in it for stardew valley.
> Start a new engine based on MonoGame.
> All is going ok? Having minor issues with getting .csproj files set up but other than that fine.
> Get advice to switch to .NET core for higher compatibility.
> Start doing that
> Doesn't work at all, random weird errors all over the place.
> ProjectIsFucked.jpeg
> Delete folders, I didn't have much anyways.
> Make some basic boilerplate for both the engine and the game like 5 times, deleting the folders and starting over because errors.
> Finally get something to almost compile.
> Reinstall .NET
> Compile works.
> Compile again
> Compile fails
> Do dotnet restore
> Compile again
> Compile fails
> Do dotnet restore again
> Compile again
> Compile works
What in the ever loving fuck.
In all seriousness, if anybody knows what in the fuck is happening, I'd appreciate the help: https://stackoverflow.com/questions...4 -
Compiling native code under Windows without using visual studio/msbuild is an unspeakable pain in the rear...3
Top Tags
Weekly Rant
View