At minute to twelve, MSBuild makes a comeback
-
@Polygeekery said in At minute to twelve, MSBuild makes a comeback:
How much more specific to Visual Studio can you get than declaring which version of Visual Studio to use when editing the project files?
You just said there's no point in debating with me. Explain to me why I should bother to reply to this when you'll just go back to insults. What's my motivation here?
-
@blakeyrat said in At minute to twelve, MSBuild makes a comeback:
You know, the conversation would go a lot quicker if you would just make your point in the first place, instead of posting trivia then waiting all day before you come back and explain what the fuck you were trying to communicate with it.
I did, It isn't my fault that you are chronically stupid.
-
@lucas1 Oh good, it's all insults now. Pile-on, everybody.
-
@blakeyrat you bring it upon yourself.
-
@blakeyrat said in At minute to twelve, MSBuild makes a comeback:
You just said there's no point in debating with me.
When you are in these moods, there is no point in honest debate with you. It can be fun to rustle your jimmies though.
@blakeyrat said in At minute to twelve, MSBuild makes a comeback:
Explain to me why I should bother to reply to this when you'll just go back to insults.
Explain to me why anyone should reply to you when you always just go back to insults.
@blakeyrat said in At minute to twelve, MSBuild makes a comeback:
What's my motivation here?
What is your motivation for anything you do on these forums? Morbid curiosity? You just like insulting people? Pendantry? Fuck if I know. I don't really care. But you were wrong, and now you should admit it.
-
@lordofduct It depends how custom the csproj/vbproj is. In anycase the csproj approach isn't going to work with non-VS / Xamarin without more plugins, which was the motivation behind moving to project.json in the first place i.e. you told it what to ignore file wise instead of telling it what it should be including.
-
@Polygeekery Keep going, pile it on. You can do better than that. You didn't even call my mom a whore.
-
@lucas1 Listen, I'm not trying to defend using the xml-based project config file, vs a json based one.
I was just interpreting the intent of the statement made by @blakeyrat.
-
@lordofduct fair enough.
-
@Polygeekery said in At minute to twelve, MSBuild makes a comeback:
How much more specific to Visual Studio can you get than declaring which version of Visual Studio to use when editing the project files?
It's a bad name for what is basically "API level". Yes, it was obviously named with no anticipation of another IDE being used, but it doesn't mean no other IDE can ever be used. They either need to use the same rules as a particular version of VS for parsing the .csproj file and declare that, or define their own version if they want any specific tags or whatever.
-
@Jaloopa I just dunno how this is going to work if you want to use a lightweight editor instead of an IDE, which is why they started changing the tooling to be more node like in the first place.
-
@Jaloopa said in At minute to twelve, MSBuild makes a comeback:
It's a bad name for what is basically "API level". Yes, it was obviously named with no anticipation of another IDE being used, but it doesn't mean no other IDE can ever be used. They either need to use the same rules as a particular version of VS for parsing the .csproj file and declare that, or define their own version if they want any specific tags or whatever.
I get that. Any other IDE or text editor could read that same XML file and do the same things that VS does. But that does not mean that
@blakeyrat said in At minute to twelve, MSBuild makes a comeback:
There's nothing in them specific to Visual Studio.
That is a bit like saying there is nothing in the WIN32 API that is Windows specific, because WINE does many of the same things. It is disingenuous at the very least.
-
@Jaloopa said in At minute to twelve, MSBuild makes a comeback:
It's a bad name for what is basically "API level".
The person who decided that GUIDs were a good idea for identifying library, API or IDE versions needs a smack upside the head. It manages to be one of the few things worse than using a git commit ID, as those are at least theoretically computable by others. GUIDs have exactly zero discoverability other than “open up an existing file and see WTF is in there already”.
-
@dkf said in At minute to twelve, MSBuild makes a comeback:
Puts working with a Maven POM in perspective, I guess.
Not using Gradle is still . Or can anyone name a reason to use Maven for a new project?
-
@asdf said in At minute to twelve, MSBuild makes a comeback:
@dkf said in At minute to twelve, MSBuild makes a comeback:
Puts working with a Maven POM in perspective, I guess.
Not using Gradle is still . Or can anyone name a reason to use Maven for a new project?
Gradle and Android Studio (used to) break hard, requiring all sorts of annoying shenanigans to fix...
-
@sloosecannon said in At minute to twelve, MSBuild makes a comeback:
Gradle and Android Studio (used to) break hard, requiring all sorts of annoying shenanigans to fix...
I have to admit that I never used it for an Android project. I haven't written a single Android app since the switch to Gradle and Android Studio.
-
@asdf said in At minute to twelve, MSBuild makes a comeback:
@sloosecannon said in At minute to twelve, MSBuild makes a comeback:
Gradle and Android Studio (used to) break hard, requiring all sorts of annoying shenanigans to fix...
I have to admit that I never used it for an Android project. I haven't written a single Android app since the switch to Gradle and Android Studio.
Yeah, I think the integration has been improved in newer Studio versions too. The issues I encountered were basically:
Android Studio needs an update
/me installs update
Your project has an old version of the gradle wrapper! You should update that!
/me updates Gradle
Your project is built for an old Gradle version! You should fix that!
/me updates Gradle version
Everything is broken!!!!!!
/me:
-
@sloosecannon said in At minute to twelve, MSBuild makes a comeback:
Your project has an old version of the gradle wrapper! You should update that!
/me updates Gradle
Your project is built for an old Gradle version! You should fix that!
/me updates Gradle version
So… It asked you to do the same thing twice? ?
-
@asdf said in At minute to twelve, MSBuild makes a comeback:
@dkf said in At minute to twelve, MSBuild makes a comeback:
Puts working with a Maven POM in perspective, I guess.
Not using Gradle is still . Or can anyone name a reason to use Maven for a new project?
Last I checked, Gradle only supports provided dependencies for war projects.
Which can be a problem if you have your Java code files in a separate project if they depend on things like the Servlet library.
-
@powerlord said in At minute to twelve, MSBuild makes a comeback:
Last I checked, Gradle only supports provided dependencies for war projects.
You could always easily add a custom configuration for that, and since Gradle 2.12, the Java plugin now finally creates one compileOnly configuration per SourceSet by default.
Edit: The first Google result for "gradle provided": https://sinking.in/blog/provided-scope-in-gradle/. Even includes a nice explanation with pictures. We used the first approach mentioned in that blog post before we upgraded to 2.13.
Edit 2: I just realized that the blog post is wrong, adding the provided configuration to the main SourceSet's runtimeClasspath doesn't make any sense. This is the correct version:
configurations { provided } sourceSets { main { compileClasspath += configurations.provided } // only necessary if your tests need the provided dependencies test { compileClasspath += configurations.provided runtimeClasspath += configurations.provided } }
-
@asdf No, I worded that poorly.
It's "Update the Gradle Wrapper", then update the Gradle version used in the config. Or something like that.
It's been a while though, and the more recent Android Studio versions are much better. But I distinctly remember Gradle causing the state of several Android projects to become
to the point where it was simpler to rebuild the project and copy the code over manually.....
-
-
@asdf said in At minute to twelve, MSBuild makes a comeback:
@powerlord said in At minute to twelve, MSBuild makes a comeback:
Last I checked, Gradle only supports provided dependencies for war projects.
You could always easily add a custom configuration for that, and since Gradle 2.12, the Java plugin now finally creates one compileOnly configuration per SourceSet by default.
Related question: Yesterday I checked that latest version of Gradle from JetBrains (Default path in Android Studio) is will v2.10. Do you recommand me edit the gradle-wrapper.properties file to use a local but newer version instead?
-
@cheong said in At minute to twelve, MSBuild makes a comeback:
Do you recommand me edit the gradle-wrapper.properties file to use a local but newer version instead?
This very much depends on how many incubating (= API unstable) Gradle features and internal APIs the Android plugin is using, which I don't know. Because those break frequently, so you should always take a look at the changelogs before upgrading. I don't have much experience with Android Studio and the android Gradle plugin, but if there's something like an official Gradle version for Android development, I'd rather stick to it for now.
-
@blakeyrat said in At minute to twelve, MSBuild makes a comeback:
just following me around to every topic and calling me an idiot in a FrostCat-esque way?
Aw, come one, there's got to be at least one or two topics a month where you don't act like an idiot and I don't call you one. Besides, I bet if someone searched the database, it'd turn out that you've called yourself an idiot far more than I have.
Besides, I prefer to call you an asshole, because it's undeniable.
-
@Polygeekery said in At minute to twelve, MSBuild makes a comeback:
Explain to me why anyone should reply to you when you always just go back to insults.
Because how else will he get his jollies from starting flamewars if people won't take the bait.