This was cool, thanks!

How I wish this has better audio. Had a hard time listening to this while driving.

Very informative and helpful

Great, Thanks for the nice video. Does Nukeeper also support SDK style projects where project references kept in single Nuget.PackageVersions.props file?

Hello! First, thank you for de video! I don't know if I will get any answer for this question, but I'll try anyway. I have a feed at azure artifacts with some nuget packages. I need to have it always updated. I'm trying to create a pipeline to update it automatically like in this video. I select the feed, but when I run the pipeline it give me the following error: "NuKeeper needs access to the OAuth token to query the API". The problem is: there isn't any slot to input OAuth token. Any idea about what to do?

In terms of optimistic concurrency- rather than executing a query to check the version and THEN appending the events to the database, why not take advantage of Cosmos' item IDs model? We know that each item needs a unique <item ID-partition key> combination, therefore by using partition keys for stream IDs, we can simply use integers (or a variation) for item IDs. Then simply execute an insert operation. If my new event is expected to be at version 5, but in the meantime a different 5th event has been already written to the stream, attempting to insert another item with ID (version) 5 will fail. This also helps to avoid a potential issue (albeit an unlikely issue) where between the time we read the current version, and the time we attempted to write to the store, another event has been added. We can avoid it because the ID-partition key uniqueness check will execute in the database. Here we have an optimistic concurrency without the need to implement it in the code.

apt install qt-creator

it would be great using mongodb, please :D

Please do more videos on this. Tutorial style video from scratch would be awesome. Maybe you can share the smart contracts that you uploaded?

Nice vid. Thanks for the updated info, because other videos are quite outdated regarding that

Does graphql dotnet support dictionary<string,string> ? if not how to create a custom dictionary using grahqldotnet?

Great!! It helped me so much! Thanks from Brazil

Is the demo code available ?

How do I get the metadata .json configuration file from visual studio code? (For example HelloBlockchain.Json)

Hi, request to make vedio on installing IS4 on Azure along with AdminUI and its DB

Thank you for this.

cool video, but have a microphone pls :(

How did you get the CLI connected to the Docker instance?

Roland has tutorials in Pluralsight about GraphQL

Thanks

In the documentation on graphql.org/code/#c-net 'Hot Chocolate' is prescribed as GraphQL Server. Is there any advantage or disadvantage using the normal GrapQL over the 'Hot Chocolate' library?

Hope you do a detailed project from scratch. Current video is just a discussion.

What about deploying? Does .qml files compile with the assembly and if it doesnt, does .qml files compile?

Very helpful and thanks for the demo code.

Please add some real world tutorials and sample projects , there is just too little documentation out there

Is the source code for the demo app available somewhere?

I tried to present end to end in my youTube channel. I discovered this later.

Improve audio please

Very good, can you please share the test code?

This could be an interesting conversation but the background noise is too much.

Super cool, thanks.

Thank you for explaining that one doesn't need to modify the client when switching to use azure, this had me stumped for a while!

When Service Fabric released, Microsoft says infrastructure provided by Microsoft, developer can only concentrate on code. They promised this is the best technology they release. Later now, with mesh, they promise the same and using Docker and container. So confusing why MS not thinking about the feature approach (docker and container already was exist while Service fabric released).

Can you please make a short tutorial how to use qml in c#. It would really help me out.

This does not show you how to run a blazor stand alone application in your browser. It shows you how to launch it in Visual Studio which is not the same thing

great video very informative

I found community support for QML very minimal about 1.5 years ago. Asking questions on Stackoverflow did not solicit any answers. Is that better these days? Besides that it's a cool idea to bring QML to .NET. Looks nice!

Interessant. Veel achtergronden en details die ik nog niet tegengekomen was.

Didn't know it existed. Great video! Love the new graphics too.

Heb ook hele grote story maps in SpecMap gezet. Werkt prima. Kolommen in SpecMap koppel je aan features, Rijen aan Iterations. Koppelen van een feature en iteration aan een product backlog item (story) zorgt er automatisch voor dat die PBI in SpecMap op de juiste plaats gezet wordt. Schuiven in SpecMap past weer automatisch feature en iteration aan. Rijen en kolommen die je even niet wilt zien kan je dichtklappen, dat houdt de boel overzichtelijk. Een (volgens mij) goede werkwijze is dat je als product owner steeds slices (rijen) uit SpecMap op pakt om samen met het team uit te werken. Alle stories in SpecMap hebben bij ons de status New, oppakken van een slice betekent voor die stories dat de Product Owner de status op Approved zet. Die stories komen voor het team dan automatisch op ons Kanban board in TFS binnen, worden door het team voorbereid, komen in de sprint en worden gereleased. Let op: werkt prima met VSTS of TFS als iedereen op zelfde domain zit. Werkt NIET met gebruikers van verschillende domains.

Vet! Goede Nederlandse uitleg waarmee iedere ontwikkelaar overtuigd kan worden om naar dotnet new te gaan kijken :)

Complimenten voor deze video, zowel qua presentatie als techniek, heb me gelijk even gesubscribed!

Leuke video! Vermakelijk en prima te volgen. Ook goed te zien dat er voor source control tegenwoordig Git wordt gebruikt :)

Wish this had been in english 😔

Aan het eind waar ik het heb over IUseFixture<T> had ik IClassFixture<T> moeten gebruiken. IUseFixture<T> bestaat niet meer in xUnit2 maar wordt wel gebruikt in eerdere versies...

Microsoft inderdaad behoorlijk aan het veranderen. ik vind dat juist een erg interessante wending hebben. benieuwd wat de toekomst van MS gaat brengen!