Relative Content

softwareengineering

Is it reasonable to use POCO’s that inherit from DTO’s?

I’m designing a tiered .NET application, and I want to use the Code First approach. I’m new to this, so I’m struggling to envision how it ought to be designed. Would the following be a reasonable approach? What problems or limitations might I run into?

ISC license advice

Is the ISC license suitable as a MIT or Simplified BSD license replacement?

How to port this architecture to .net?

My team is currently locked into using a tool we dislike that takes the form of a Eclipse plugin and a .jar; the plugin gives us a button to quickly run a single file’s code (via invoking the main .jar and passing to it the current file). We want to move to C#.net. Is there any way to get Visual Studio to replicate this behavior? Obviously we could put each runnable class into its own project in our solution, but that requires checking a lot of project files into source control. Ideally we’d have a main() method in each file and could tell visual studio to run just that file for development purposes, while the finished software would be run from a single entry point using command-line parameters.

Give open-source developers a free license for my commercial software?

I am creating a software package that will be useful to programmers, engineers and scientists. List price will be in the region of $1,000 — way beyond the budget of most open-source developers, hobbyists and enthusiasts. So I am considering two things, the first generous, the second maybe a little greedy:

C++ Class Initalization

I’m a python programmer who sees a lot of C++ code but doesn’t know the language and there seems to be two ways to initalize a class. I was hoping that someone can tell me the difference.