![]() Build times are vastly improved, although one problem we have seen is that Intellisense fails for types defined in projects that are not in the current set. Any projects that we are working on get added in to this. To help with this, we usually create another 'current working set' solution file. Building this takes a long time, even if the projects themselves have not changed. Our way of structuring projects relies on a single solution file. We have a completely flat structure but name our project files, assemblies and namespaces the same. Deeply nested folders just increase the time it takes to find anything. One person's folder structure is another's nightmare. Are solutions folders a good way of organizing stuff? This helps prevents issues that occur when the developer setup is different from the deployment setup.Ĥ. The idea being that this folder is the same as when the software is deployed. Should every project build to its own folder, or should they all build to the same output folder(they are all part of the same application)Īll of our output is put in a single folder called 'bin'. The extra copying just adds to the build times.ģ. Specifically, he will demonstrate two ways to w. If 'project' is selected, then the dependency is added to our single, global solution file by default. In this video, Sayed Hashimi will show you how you can work with multiple solutions in Visual Studio for Mac. We use the 'add reference' context menu option. How do you best handle references between projects ![]() To answer the original questions based on our experiences:ġ. We have a similar problem as we have 109 separate projects to deal with.
0 Comments
Leave a Reply. |