D
Davis Ford
Hi, I have a DLL project that implements the Model/Controller part of
MVC, and the client of the DLL would be the View. The interface the
View consumes is the Controller API, and the Model is marked internal,
b/c the View shouldn't need to get at it, but this means I can no
longer test the Model unless my NUnit tests exist inside the DLL
project.
This has the unwanted side-effect of having to deploy nunit.framework,
nunit.core along with the DLL.
If I move the tests out into a separate project, the NUnit tests that
run against the model no longer work b/c the model is not accessible.
Is there some compromise to this solution? Is it possible to fiddle
around with VS2005 DEBUG/RELEASE settings to solve this, or is there
another way?
Thx in advance,
Davis
MVC, and the client of the DLL would be the View. The interface the
View consumes is the Controller API, and the Model is marked internal,
b/c the View shouldn't need to get at it, but this means I can no
longer test the Model unless my NUnit tests exist inside the DLL
project.
This has the unwanted side-effect of having to deploy nunit.framework,
nunit.core along with the DLL.
If I move the tests out into a separate project, the NUnit tests that
run against the model no longer work b/c the model is not accessible.
Is there some compromise to this solution? Is it possible to fiddle
around with VS2005 DEBUG/RELEASE settings to solve this, or is there
another way?
Thx in advance,
Davis