Organization of deployed code and unit tests - best practices?

Oct 12, 2015 at 8:00 AM
Edited Oct 12, 2015 at 8:01 AM
I'm looking for some feedback/advice on organizing my actual app code (which gets deployed) and my tsUnit-based unit test code (that is only needed internally for testing purposes). The application is a client/server app where the client is built in TypeScript and communicates over a web socket with the C#/.Net-based server.
I'm using Visual Studio 2013 and currently have a single "HTML Application with TypeScript" project in my solution, which I intend to use for the production app (the server is currently in another solution). I am planning to now create a second project in the solution which will contain the unit tests for the client side code (TypeScript). This way, I've got everything in 1 solution, and keep the unit tests out of the deployed production app.
Perhaps I should also move the server code into the same solution as the client code.

How do people here organize their production and unit test code?
Any advice/tips welcome!

Edit: If there are better places to ask these kinds of questions, please tell me so.