I’m not sure when you last used C#, but solutions are only used if you want to group 2+ separate projects together, are fairly intuitive (there’s a single unintuitive bit—running the main project doesn’t rebuild the others, but it DOES pop up a warning to that effect), and I don’t think I’ve ever seen someone struggle with them outside of the complexities of a multi-user office where the solution file is stored in subversion (solved by not storing solution files in SVN!)
Equally, I’m not sure why the ”.NET framework” would add any complexity. The ability to look at a control in a UI and see all of it’s attributes is something most people find a lot more intuitive. The ability to double-click a control and add an obvious default event is also very helpful, in my experience with teaching.
Header files, I will concede. For basic programs, C# automatically includes the necessary ones, however—so it’s not something that really comes up until you’re doing more advanced code.
I’m not sure when you last used C#, but solutions are only used if you want to group 2+ separate projects together, are fairly intuitive (there’s a single unintuitive bit—running the main project doesn’t rebuild the others, but it DOES pop up a warning to that effect), and I don’t think I’ve ever seen someone struggle with them outside of the complexities of a multi-user office where the solution file is stored in subversion (solved by not storing solution files in SVN!)
Equally, I’m not sure why the ”.NET framework” would add any complexity. The ability to look at a control in a UI and see all of it’s attributes is something most people find a lot more intuitive. The ability to double-click a control and add an obvious default event is also very helpful, in my experience with teaching.
Header files, I will concede. For basic programs, C# automatically includes the necessary ones, however—so it’s not something that really comes up until you’re doing more advanced code.