<story><title>C#88: The Original C# (2018)</title><url>https://medium.com/@ricomariani/c-88-the-original-c-66a1b5de47d7</url></story><parent_chain><item><author>james_s_tayler</author><text>Is this related to C# having this structure where everything is split into hundreds of csproj files and multiple solutions?&lt;p&gt;And this must be related to needing to have pdb file or being unable to debug.&lt;p&gt;I wish those two things were not the case. And nuget.&lt;p&gt;I find C# wonderful except those particular decisions give me pain on a daily basis.</text></item></parent_chain><comment><author>jaabe</author><text>I think splitting into projects with their own separate dependencies is&amp;#x2F;was actually one of the few advantages to C#, because it lets you replace an entire project and it’s dependencies seamlessly.&lt;p&gt;This has been extremely handy for us as we’ve been slowly upgrading to .net core. Because we can literally do it one project at a time without even risking breaking anything. Before going to .Net core it made switching from Web Forns to MVC really, really painless because all the business logic lived in its own projects, allowing us to run and maintain the Web Forms project, while building its replacement within the same solution.&lt;p&gt;I guess it requires you to think about the architecture of your solution, but what stack doesn’t? I say “is&amp;#x2F;was” an advantage though, because it’s primary use cases are frankly mostly related to the past or really bad practices. It allows you to keep a single project running on some really old .Net version, to utilise something legacy. That’s bad, but sometimes it has real works value, even if it’s bad.&lt;p&gt;NUGET has been fairly terrible though, and despite its many improvements, frankly continues to be so.</text></comment>
<story><title>C#88: The Original C# (2018)</title><url>https://medium.com/@ricomariani/c-88-the-original-c-66a1b5de47d7</url></story><parent_chain><item><author>james_s_tayler</author><text>Is this related to C# having this structure where everything is split into hundreds of csproj files and multiple solutions?&lt;p&gt;And this must be related to needing to have pdb file or being unable to debug.&lt;p&gt;I wish those two things were not the case. And nuget.&lt;p&gt;I find C# wonderful except those particular decisions give me pain on a daily basis.</text></item></parent_chain><comment><author>ygra</author><text>(a) How you structure larger applications into projects (assemblies) is largely your own problem. If you have a component that&amp;#x27;s intended to be used from different projects, then it sometimes makes sense that it gets its own project as well. However, you can just as well cross-include the source file if you want. There aren&amp;#x27;t that many things that explicitly require separate assemblies.&lt;p&gt;(b) Debug symbols have to be there for you to be able to have source-level debugging, of course. You can always debug the assembly code, of course. For Microsoft&amp;#x27;s tooling, PDB files are the debug symbols that link the assembly code to the source code. Other tools sometimes embed debugging information in the binaries. And if this information isn&amp;#x27;t there, you can&amp;#x27;t have source debugging either.&lt;p&gt;(c) No one&amp;#x27;s forcing you to use NuGet, although I wonder what you particular problems are with it.</text></comment>