But what happens when you try to use CC.NET with a solution that has managed and unmanaged code (and more important, does not contain explicit dependencies between some projects)? The problem is that deven.com will not compile the projects in the solution in the correct build order. Eventually you will have to fix the VS solution and set up the correct dependencies, but there is a workaround. Just create a
Saturday, June 20, 2009
More on CC.NET
CC.NET is a really cool technology. Now that I have it running, I don't have to worry or spend time creating installers. It can do everything: compile your VS solution, run automated tests, obfuscate and lock the assemblies, and create an installer.
But what happens when you try to use CC.NET with a solution that has managed and unmanaged code (and more important, does not contain explicit dependencies between some projects)? The problem is that deven.com will not compile the projects in the solution in the correct build order. Eventually you will have to fix the VS solution and set up the correct dependencies, but there is a workaround. Just create a task for each project and CC.NET will compile the projects in that order. The drawback is that you may end up with quite a few tasks, depending on your project.
But what happens when you try to use CC.NET with a solution that has managed and unmanaged code (and more important, does not contain explicit dependencies between some projects)? The problem is that deven.com will not compile the projects in the solution in the correct build order. Eventually you will have to fix the VS solution and set up the correct dependencies, but there is a workaround. Just create a
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment