I wonder if I can get some feedback from people about the best way to create Visual Studio solutions.
My basic requirements are to ensure that any code / tests will run against the right resources, in particular the database schema and sample data.
I tried various ways to do this with mixed degrees of success. Currently, I ...
- Create a * .Installation.dll class library that creates, configures, and populates the database, etc.
- Have a * .Build.dll class library that has an MSBuild task that takes parameters from the csproj file and goes to the Installation.dll file.
They are sitting in their own decision. Tell MyApp.Build.sln. I keep this separate from my main solution to prevent file locking issues.
In my main solution, say MyApp.sln ...
My test projects then invoke the MSBuild task to create test environments for integration testing, including the database and test data. And my front-end Web / Windows projects cause the creation of MSBuild to create managed environments for test users / my testing manually
So, I use MSBuild to create custom builds / environments for testing / working. In addition, I can wrap the Installation.dll file in a configuration / configuration tool to automate the installation for the user when the time comes for the installation.
? , . , (, , , ..), , .
SubVersion TeamCity. CI , daily/commit build. TeamCity , / .. ?
.