Earlier quoted context omitted.
> C# is only really practical for Microsoft's platforms. Not necessarily. If you're doing game development with Unity3D, for example, you're probably going to write much of your game in C#, and it's going to run on Windows, Linux, OS X, Android and iOS.
Wish it was true. It has never been true and it is unlikely to be true in near future. Try some non toy F# on windows and on Mono and you will know. Mono leaks, and if you rely on correct behavior of tail calls, you are in for a lot of grief.
C# Tutorials
61–66 of 66 posts
Re: C# Tutorials
#62DO NOT USE!! This is from Visual Studio 2003 and will be a terrible, terrible guide. Yes, that's 2003, over a decade ago. C# programming has moved far away from the Java inspired boiler-plate of that time (as I assume Java has). For example the properties tutorial is completely wrong as it doesn't include the new simple syntax which you should be using 95% of the time `public string Name { get; set; }`. Also the way…
Here's the updated version of the C# Programming Guide for anyone interested: http://msdn.microsoft.com/en-us/library/67ef8sbd.aspx
Thank you for this link!!
Re: C# Tutorials
#63Earlier quoted context omitted.
Here's the updated version of the C# Programming Guide for anyone interested: http://msdn.microsoft.com/en-us/library/67ef8sbd.aspx
Thank you for this link!!
If you are willing to invest a few bucks, http://www.albahari.com/nutshell/ is a comprehensive reference and good introduction for c# and the .net framework.
Re: C# Tutorials
#64Re: C# Tutorials
#65Re: C# Tutorials
#66I'm still confused by the use of '.' to conflate namespaces & classes, and other things together. A separate character, like ':' or something else would've helped me :) Or GACs, or finding the right System.Data.SQLite module for your app - http://system.data.sqlite.org/index.html/doc/trunk/www/downl... Or figuring out how exactly deployments/setups work - where things get put, etc. I don't know much about java - but…
On the GAC: Never use the GAC -- except for platform libraries (System.*, etc.). Always deploy your dependency DLLs side-by-side with your code.
I know that now, but there are still some .NET developers that I meet that think this is the way to go.
Another problem with .NET is that there is a lot to learn, then unlearn - language, api, frameworks, deployment-wise.
That by itself is not bad, if you are an active developer, but if you just given few times a year to fix this and that C# project, then it's a bit more painful.
For example I have to upgrade 32-bit app using Antlr3 and system.data.sqlite (matching 3.7.0.1) to 64-bit, antlr3 newer version and system.data.sqlite (matching 3.8.2) - and after the upgrade there is significant slowdown, and some things do not work (possibly sqlite, but who knows for sure).