While working with Visual Studio in general (or Visual C # Express in my special case), it seems that each project can be configured.
Produce only one output - such as an executable or a library
I work on a project I have been having a shared library and some applications, and I already have a project in my solution for each of them. However, during development, I find it useful to write short example programs which is a small subsystem Can run At the level of the unit tests which are not)
Is there a good way to handle this visual studio? I would like to avoid adding several dozen different projects to my solution for every short test program, especially when these programs are usually less than 100 lines I hope to find something that continues to work in Visual Studio And I'm using (instead of doing something like) to use its build system.
I can have an answer like this:
- A method of setting up this visual studio that I have not yet received < Li> A GUI such as the graphical runner of NUnit that searches for an assembly for classes with defined main () functions Command> Post Text "ItemProp =" Text ">
Instead of writing a small test program, consider writing a unit test, which takes you directly into it.
You may need several unit tests as a test project.
Comments
Post a Comment