project-organization

问题 I'm currently creating a paired unit test assembly for every assembly in my project, both are in the same folder. MyProject/MyProject.csproj MyProject.Test/MyProject.Test.csproj Looking at open source projects, I've seen some smaller project put all tests in one assembly, and other split it out like mine. I'm dealing with a large solution so it would be pretty crazy to put all tests in one project. I currently have msbuild logic to run tests on all *.Test.csproj files. If I had all my tests

问题 One of the popular way to organize project directory is more or less like this: MyLib +--mylib_class_a.h mylib_class_a.cpp mylib_library_private_helpers.h mylib_library_private_helpers.cpp MyApp +--other_class.h other_class.cpp app.cpp app.cpp : #include "other_class.h" #include <mylib_class_a.h> // using library MyLib All .h and .cpp files for the same library are in the same directory. To avoid name collision, file names are often prefix with company name and/or library name. MyLib will be

问题 What is the best way to organize the files in your project? For example do you put all user controls in a separate folder or do you place them in a sub folder? Do you have business logic folder? A helper classes folder? I used to organize my projects like this: Project/User Controls/Module Name/ Project/Classes/Module Name/ Now I am learning more towards something like this: Project/Module Name/User Controls/ Project/Module Name/Classes/ What is the best way? Especially if the project gets

问题 In Visual Studio 2010 I have a large solution that contains number of .cs files that are no longer used (not referenced in .csproj), but still present in code repository (ClearCase). Do you know of any tool / extension / script that would find all such files? One could write a script that goes through all projects' directories, takes all files that are checked in and than compares against content of a project file. In it is not there, than we have a candidate for deletion. It is not too

问题 I'm starting a Python project and expect to have 20 or more classes in it. As is good practice I want to put them in a separate file each. However, the project directory quickly becomes swamped with files (or will when I do this). If I put a file to import in a folder I can no longer import it. How do I import a file from another folder and will I need to reference to the class it contains differently now that it's in a folder? Thanks in advance 回答1: Create an __init__.py file in your

问题 I have the following projects/assemblies in my solution: Entities ; It is a class library that contains two classes: Account and AccountDetail . Account class has a property Details which is of type ObservableCollection<AccountDetail> and I use it to store the details of the account object. Core ; It is a class library that contains one class: AccountController whose purpose is to get the data from the Sql Server and to populate the Account objects (alongside the AccountDetail collection

问题 Thanks in advance. I have some Aggregates in the Domain Layer library. Also, some DTO s in a separate library, which is shared between Server and Client side. An Aggregate of an entity is more informative than its DTO . So, in order to convert from DTO to Aggregate , a repository should be accessed by a Dto Assembler . Interfaces of repositories are in Domain Layer . That's why i come to conclusion that DtoAssembler should be a part of DomainLayer . Is this right? 回答1: No, this would be plain

问题 So I have a DataEntity class generated by EntityFramework4 for my sqlexpress08 database. This data context is exposed via a WCF Data Service/Odata to silverlight and win forms clients. Should the data entities + edmx file (generated by EF4) go in a separate class library? The problem here then is I would specify data annotations for a few entities and then some of them would require specific MVC attributes (like CompareAttribute) so the class library would also reference mvc dlls. There also

问题 I'll preface this by saying that I usually work in C#/.Net. Normally, I use a naming scheme that puts common, reusable components into a namespace that reflects our organization and project-specific components into a namespace tied to the project. One of the reasons I do this is that I sometimes share my components with others outside my department, but within the organization. Project-specific namespaces are typically prefaced with the name or abbreviation of the department. When I reuse

问题 I've written some Delphi code I would like to share on GitHub. All code is contained in runtime and designtime packages as required. There are many "Project Options" to set for each project. (Output directories, search paths, compilation options, etc.) I've managed to find some default options that work well for my situation but reading other Q&As here it's clear there are multiple ways of working. What project options should be used to allow the open source packages to easily be incorporated