Phew. Good to hear that you’re alright.
1 Like
Anybody wondering if the XNA books are still worth investing into? I bought pretty much all of them… hoping to get around to it soon… and may start building a tutorial of sorts, soon…ish… any interest?
How is everyone? any notable projects atm?
In case you missed it:
Any good tips for a Monogame beginner?
Good communities? Good tutorials? Good libraries? Good tools? Discord? Gitter?
Things to look out for?
Take a look here:
Regarding the other stuff, links are on the home page of the website…
There are two main threads and Extended has it’s own filter on the forum…
Yeah I linked the thread which links the last post, have to click the top post for it to link the top, can get confusing sometimes haha…
I suggest getting familiar with the basics before delving into the extensions and third party ‘add-ins’ if we can give them such a title…
You can code whatever you are capable of and create your own add-ins or extensions or engines, there are many useful resources out there [mainly books] that can help you have an idea of what is involved in making a game engine and the like…
Only you are the limit to what you can create…
Also in case I missed it, Welcome to the forums!
Halfway reading your last post I felt like you were writing a book or article or something, but figured you were just getting started with coding, right?
Thank you for the information! Hm, looks like I accidentally deleted my post while fiddling around with editing it on my phone… 
Thank you for the welcome. Yes, I am new here. I’m fairly experienced in programming, but not game programming (I’ve made small games with Flash and Phaser). Right now I’m just trying out different frameworks/engines to see what I like but do not know what I’m doing yet.
1 Like
Always good to have new members here, hopefully have the time to develop more myself soon…
Should I start making time for my XNA to MonoGame projects or is nobody interested in more, useful MonoGame code/tutorials?
Writing seems to take a back seat now, novel writing might need to take a back seat for a while I guess…
Hmm…I also want to help grow this community, ideas are welcome…
So, it appears as, ANY MAC will do for VS2017, to just access the build tools on the Mac, looks like I will be getting a MacBook Air soon… cheapest, naturally… time wise, not flustered… but it does mean I can write those XNA dev tutorials soon…
So many projects, so little time… I took a little break from my ARPG prototype to write a tutorial, but am struggling with a text. Doesn’t help that rbwhitaker and riemer’s tutorials are far better already… X)
When I finish beginner’s tutorial, I’ll need to deal with the animations in game. Hoo boy. At least @nkast wrote some tools which will ease it a lot… (shoutout to your Aether 
)
1 Like
A sad day indeed…
This makes me feel ill to say but it’s finally here…
Thank Frick I didn’t buy the previous gen model a few months back… but then this also got upgraded…
So now I just need to decide my deal with the devil and how many kidneys I plan on parting with, perhaps six… >.<
Interesting!
I think this is the follow-on video
Their interactive video page
For those of you wondering how it was done in the golden era:
C#8, some interesting new features…
EDIT
Also Visual Studio 2019 info in December…
Default implementations of interface members
Today, once you publish an interface it’s game over: you can’t add
members to it without breaking all the existing implementers of it.
In C# 8.0 we let you provide a body for an interface member. Thus, if
somebody doesn’t implement that member (perhaps because it wasn’t there
yet when they wrote the code), they will just get the default
implementation instead.
interface ILogger
{
void Log(LogLevel level, string message);
void Log(Exception ex) => Log(LogLevel.Error, ex.ToString()); // New overload
}
class ConsoleLogger : ILogger
{
public void Log(LogLevel level, string message) { ... }
// Log(Exception) gets default implementation
}
Correct me if im wrong …
Virtual interfaces ?
Isn’t this the equivalent of introducing multiple inheritance with abstract classes ?
What happens when two interfaces define the same default and its not overriden by the deriving class ?.
interface ILogger
{
void Log(LogLevel level, string message);
void Log(Exception ex) => Log(LogLevel.Error, ex.ToString()); // New overload
}
interface ILoggerB
{
void Log(LogLevel level, string message);
void Log(Exception ex) => Log(LogLevel.Error, ex.ToString()); // New overload
}
class ConsoleLogger : ILogger : ILoggerB
{
public void Log(LogLevel level, string message) { ... }
// Log(Exception) gets default implementation
// but which one ?
}
Granted not a great naming example but the question remains
Switch expressions
I like this because i use switch case from time to time. Actually i really like this one a lot.
yeild
I hardly ever use this because i think that changing the normal way method scope works in general leads to bugs and is hard to debug. When there is a problem in general it can add a huge amount of complexity to code and i cant even remember the last time i used it. That said it does look pretty neat.
Note.
Most of the C# 8.0 language features will run on any version of .NET. However, a few of them have platform dependencies.
Async streams, indexers and ranges all rely on new framework types
that will be part of .NET Standard 2.1.
,
.NET Core 3.0 as well as Xamarin, Unity and Mono will all implement
.NET Standard 2.1,
but
.NET Framework 4.8 will not.
This means that the types required to use these features won’t be available when you target
C# 8.0 to .NET Framework 4.8.
Yeah, this part bummed me a bit, but I will see what benefits .Net Std 
2+ and Core 3+ bring and relearn that soon…