Skip to main content

OK let's give LiteDB (File-based #nosql DB written in #dotnet ) a whirl:

I experimented with that too. I actually had been using a JSON file for persistence during prototyping. So it sort of felt easier to use a document store.

Thanks to some big help from @dwuk86 my tutorial from earlier is much cleaner and should be less chatty on the eventing system. #avalonia #dotnet

While prototyping some UI concepts I wanted to do the same "infinite scroll" as you get in #twitter #diaspora etc. Here's how you can get something like that working with #avalonia #dotnet :

Ah, I see. It's more a matter of how badly others like Twitter do it. I don't use Twitter, but I get the basic idea from the inscrutable ordering/visibility algorithm Facebook uses.

Of the "big" for-profit social media platforms, the one I tend to use is tumblr (although calling tumblr "for-profit" is more of a hilarious joke about venture capitalism than anything else). Famously, tumblr uses strict reverse chronological order. It's a pervasive joke that tumblr is a "hell site" that proves how much we tumblr users will put up with just for the sake of a reverse chronological order dash.

@Hank G Thank you much for the explanation. Always learning :)

Today was going to be a big day of breaking ground on a new #dotnet library. Instead I spent half of it figuring out how to do local package publishing with NuGet on #linux. Here's a tutorial so you can figure it out in a fraction the of the time.

"only" 3 hrs to get local NuGet Package installs working with #dotnet under #linux. It's not hard it's just beyond not well documented *and* once again the non-Windows toolchains are second class citizens unfortunately :(. Need to document in a blog post...

The hoops you have to jump through in #dotnet to do local package installation that is as simple as 'mvn install' with #java is **astounding**...smh...

André E. Veltstra reshared this.

In defense of #dotnet local tools are brand new, and even global tools are relatively new. I'm sure when more people stay using them, they'll become easier to use with updates to .Net Core

I'm trying to do local library not tools management but I think the thing that was most frustrating is that I have to install a whole mono toolchain just to manually download nuget.exe so I can do a one line command that should probably be in `dotnet nuget` already...

What exactly are you trying to do? In my experience dotnet add package worked for me without mono.

Alternatively, you could try paket as an aforementioned local tool

I'm trying to publish a package for use locally. `dotnet push` as far as I can tell can only work with a properly setup nuget server. I'm writing up a tutorial on how I got my setup working.

Try installing local packages using Gradle for Java. Better yet: have a mix of local packages, packages hosted locally on an Ivy repo, and packages hosted remotely on Maven or Bintray. Because that's where I'm at.

I bet it's equally astounding.

I've never had a problem with that actually. If I recall correctly I used the Maven plugins so it was Maven that was doing the local repo management though. I will say that I'm far more used to Maven than Gradle for larger projects. Those systems aren't perfect either for sure.

Avalonia (Windows/Mac/Linux WPF-style UI framework for .NET) is getting bumped to 0.9 and .NET Core hit 3.0. Here are some notes I have from migrating my tutorials to the new versions. #dotnet #programming

Microsoft is doing a #dotnet survey on cross platform development. Now that I have a real solution for that thanks to #AvaloniaUI I was very happy to put in my thoughts on it :)

I think I'll be trying this in my next console app. Gets rid of so much settings boilerplate! Thanks @shanselman #dotnet

I'm currently using Argu in the F# world. However now I need to take a look at this

Just used it in my first app and it worked pretty well :)

How have I never heard of this before? This looks really neat! #dotnet

Indices and Ranges for working with arrays (and lists etc?) in C# 8 look pretty neat! #dotnet #programming

.NET Core 3.0 adds even better native library integration. In case it wasn't far enough ahead of the JVM's! Even more excited if the rumored Java Interop comes to fruition next year as announced! #dotnet #java

A really good best practices article on fixing performance problems in your #dotnet application
# #dotnet programming

Having a look at #dotnet event handling overhead and scalablity from 1 to 1 billion handlers
#dotnet software

I woke from a dream where the #diaspora API was being deployed (which I think may actually be happening soon, right #diaspora-dev ?) so I revived my website comments system based on the API, polished up the #kotlin implementation, and then also wrote a #dotnet version so I could make an #fediverse app in #AvaloniaUI . Yeah I'm in a coding mood :).
#diaspora #diaspora-dev #kotlin #dotnet #fediverse #AvaloniaUI fediverse programming

yep, it should happen soon ;)

Want to use a TreeView control in #avaloniaui #dotnet? Here is a tutorial on the ins and outs of using it:

A tutorial on getting started with DataGrids in Avalonia #avaloniaui #dotnet

First article on using grid layouts for creating #avaloniaui #dotnet interfaces

A follow-up article on binding button commands/status in #avaloniaui #dotnet