I too like both, but as you tell from the post, I use less C# recently for web development.
With the C# ecosystem there is more stability and often better introductory resources for learning. Most innovations will come out for .Net via Microsoft in some form or another (either 'in-housing' an existing community project or just plain reinvention). This 'Wise Parent' model of .Net community stewardship is both its greatest strength and its greatest weakness.
.Net and Microsoft are now starting their own package management project (brought in-house again) and it will be interesting to see how that works out. Their MVC framework is very good, produced in this model, but I can't help feeling the 'mainstream developers' that buy all those Visual Studio licenses aren't that interested.
With the C# ecosystem there is more stability and often better introductory resources for learning. Most innovations will come out for .Net via Microsoft in some form or another (either 'in-housing' an existing community project or just plain reinvention). This 'Wise Parent' model of .Net community stewardship is both its greatest strength and its greatest weakness.
.Net and Microsoft are now starting their own package management project (brought in-house again) and it will be interesting to see how that works out. Their MVC framework is very good, produced in this model, but I can't help feeling the 'mainstream developers' that buy all those Visual Studio licenses aren't that interested.