project-structure

I'm a stickler for good Visual Studio Solution and Project structures. I'm about to start a WPF proof of concept piece of work. Can anyone recommend some WPF Project structures they have used and found worked well? Here http://drwpf.com/blog/2007/10/01/58/ They have one recommendation which I like: Root - Pages - Controls - Resources App.xaml Where Pages, Controls and Resources are folders. Has anyone found certain structures work well / don't work well? Also I'd rather not get into a 'Model View Presenter' discussion if that's ok with you guys. I agree with alimbada. We have also created

I'm new to Python and I'm starting a mini Project, but I have some doubts on how to organize the folders in the "Python Way". I'm using PyDev in my Development Environment, and when I create a new project a folder is created called src + src Now, in the PyDev , I can create Pydev Module and PyDev Package I need to organize my Project in the following way: + Indicators - Moving_averages.py - Stochastics.py + Strategies - Moving_averages_cross.py - example.py How can I organize this in terms of Modules and Packages? What is the meaning of Modules and Packages? Best Regards, A Package is

Is there any advantage to leaving the Scripts folder where it is in the default ASP.NET MVC Project structure. In my mind it makes more sense to create subfolders for scripts, css files, and images under the Content folder. Any downside to doing this? In short, no, there is no real downside to doing this. It is how I have been structuring my MVC projects. There are some advantages to doing this, actually... on many projects I am serving up all of the static content from a separate domain, so grouping all of the static content into a single folder has made the QA/production deployment process

I have multiple entry points in the same module. For example I have an Home entry point for the home page and an Admin entry point for the admin page. <entry-point class='com.company.project.client.HomeModule'/> <entry-point class='com.company.project.client.AdminModule'/> The way I am setup now - I need to check somt like this in my OnModuleLoad: if((RootPanel.get("someHomeWidget")!=null)&& (RootPanel.get("someOtherHomeWidget")!=null)) { // do the stuff } in order the the Admin Entrypoint not to be executed when the Home page gets open and the other way around. Not doing the check above also

In my ASP.NET MVC web application, I have: Domain Model, created by LINQ to SQL Repositories such as UserRepository and OrderRepository IQueryable Fluents as IQueryable Extension Methods such as public IQueryable<Order> GetNewOrders(this IQueryable<Order>) Services such as UserService and OrderService Utility Classes and Extension Methods such as CryptoUtility (doing Hashing etc.) and String etc. extensions ViewModels which are special for each MVC View The ASP.NET MVC project itself (Controllers, Views) I'm looking for the best project structure/organization for my case, especially separating

I'm trying to import a project from VCS (well, I'm doing it for the first time actually) and this is my (imported) project's structure: BTW. this screen is made after many tries of changing these directories' properties (in their context menus). In these source files' I have a following error: One time it had nothing against badugi.client but it reported this error only in badugi.server . I have completely no idea how it works... Also classes in the same directories do not see each other. This is a code from ClientWorker class which is located (as you can see in the first image) in the same