Make it crazy fast, cs based instead is csproj based (dotnet build MyBuildInAspire.cs). Free lunch: Finally the equivalent of javac, gcc, go build, rustc, swift [srcfile]. Yes, this would be a breaking change and I am totally fine with it. Make .NET cool/modern, with Aspire.

Next idea for @davidfowl: create a code first build system in Aspire. Mark MSBuild as legacy/obsolete. Stop the XML magic, way too complex resolvers and relative slow build times.

My guess is that is has something to do with ingress, websockets or auth. What is the best way to get help here? I can file an issue but its very hard to explain :(.

My favorite talks were from @Aaronontheweb, @kenny_baas, @ecampidoglio and ofcourse Bart de Smet. Sorry @jfversluis 😉, I do like your YT videos though!. #techorama #Microsoft.

To end on a positive note: I really liked the venue, I liked the atmosphere, I liked the networking, seeing old collegues and seeiing familiar faces that I only know from Twitter or GitHub (also real engineers ;)). Big big thanks @TechoramaNL.

Developer conferences are meant for professional engineers and other technical roles, not for managers and also not for 'pre-juniors'. There are lots of conferences that are tailored for managers and other, please don't mix it. And for pre-juniors we have schools and YT.

I hate that our industry is full of evangelizers (*kuch MVP's*) that are copying existing talks from for example Microsoft engineers or PMs and earn a lot of money with it. I've seen those videos as well. They are just walking marionette puppets imo, sorry.

Of course talks about internals and intrinsics, whats under the hood, how it *actually* works are really, really nice and I enjoy them a lot but I like case studies and high quality non technical talks as well.

Note: deep dives don't always need to be technical. Talk about backgrounds, the story and origins, about the process, about experiences, mistakes and learnings et cetera.

I think there are way too many 'Getting started' talks or even worse 'Money driven' talks. So please quit with the sales pitches and 101 tutorial talks. I will look those up at @YouTube, @ch9 etc from the original authors. I dont pay 400 euro per conference day for that.

Personal (maybe unpopular) opinion after @TechoramaNL: Sessions at developer conferences should be always deep dives (level advanced, 300+). #techorama #techoramaNL.

The only thing I want to do is to create a JWT token for api access, but there are a *lot* of ways to do this (I have 3 versions here, but I think there are more ways). On the internet there does not seem any consensus about this and I cannot find anything on MS Docs.

I think the hardest question will be: how on earth will you make this fit? New keywords, new concepts or try to reuse existing ones? . In a perfect world you do not want to change the prog lang at all and 'just' bring the implementation one level deeper (from compiler to runtime).

I know the limitations in the old days, that it was too hard and too risky to build it in the runtime because of .NET Framework etc, but I really hope now is the time to build this in the runtime instead of all the compiler machinery and trickery.

I really hope that MS is working on this in some kind of (secret) working group (virtual/green threads/coroutines). Async/await as a concept was great and .NET pioneered it in some way but the current implementation really feels outdated. @davidfowl @jaredpar @MadsTorgersen.

I know its insanely complex and I know something about props, targets, SDKs, RAR etc but I'm confident you can do this. I'm fine with breaking changes as long as we can have a hybrid solution.

Also the missing build conventions are a pity in the .NET ecosystem (=> poor mans build.cmd/sh) and then my last wish: please kill sln files 😁.

MS is doing great things in order to make .NET simple and easy (for newcomers) but MSBuild is just too complex. I know its hidden for newcomers but when you build a real product you will eventually end up in the snake pit thats called MSBuild.

I love the work MS is doing on a platform level and I love the great convergence and great release of .NET 6. The only thing that's left now is "MSBuild Core". NET really needs a new/modern build system, not relying on ancient XML magic //cc @davidfowl @DamianEdwards.

So nice!! Also the inverted mode thats suggested. Please make this happen for VS @gotheap @shanselman.