c# - Why and when should I ever be using .sln files? -

c# - Why and when should I ever be using .sln files? -

i understand solution file contains grouping of other projects why ever want have grouping of projects in single file? company work @ uses not seeing why.

another thing noticed can run .sln file happening when file beingness executed? did do?

so main question why store multiple projects in single .sln file rather of work in 1 project?

reasons might want multiple projects in single solution:

different projects can have different dependencies (either dependencies other projects in solution, or commonly, dependencies third-party dlls.) different projects can different types - console app, dll, web service, etc. different projects can have different pre/post-build steps some of projects might not implemented in c#. can have c++, vb.net, etc., projects in same solution well. different projects might components reused various other teams. many other reasons

thus, makes sense able grouping multiple projects together, such can open whole group, nail compile compile of projects in appropriate order (which can important, if instance, 1 of projects builds dll project requires dependency), launch of them specify.

when open solution, that's does: opens each of projects contained in solution in single visual studio window, along metadata how compile solution, project should launched when nail run, etc.

c# solution