3 ms·

As an outsider (largely worked with PHP/Java codebases, recently started C#/.NET Core), the naming conventions are awful. I'm still not sure what the difference

As an outsider (largely worked with PHP/Java codebases, recently started C#/.NET Core), the naming conventions are awful. I'm still not sure what the differences are between: * ASP.NET * .NET MVC * .NET 4.5 * .NET WCF * WPF It's a nebula of names, but I've been ridiculously productive while trying to grasp .NET core. I'm currently trying to make a job to take DB data and dump it on Elasticsearch. It honestly feels like PHP7 with async, it's great

efdee 10y ago
* .NET 4.5 = v4.5 of the .NET framework * ASP.NET = Web subsystem of the .NET framework. * ASP.NET MVC = MVC framework that is part of ASP.NET (not ".NET MVC") * WCF = Communications subsystem of the .NET framework (not ".NET WCF") * WPF = Presentation layer subsystem of the .NET framework
nathanaldensr 10y ago
It basically comes down to named groupings of assemblies. They are really just marketing terms. I consider the .NET Framework to encompass all .NET assemblies shipped by Microsoft in the System and sometimes Microsoft namespaces. The ones you listed are simply groupings that Microsoft considers important enough to create project templates for, have forums dedicated to each, produce examples for, etc.