legacy

I've inherited a legacy web application that has no unit tests in it. I'd like to add some, but am at a loss of where to start. Should I add them to old code? Or just new code going forward? What if that code interacts with legacy code? What would you suggest? First, I would recommend unit testing all changes going forward, I think most everyone would agree this is a good idea for regression. However, for existing code, this is one of those situations where you need to look at how much risk you're willing or allowed to introduce into the product. The problem is that when you start to unit test

At the moment, we have to build an application which is based on a legacy one. Code for that old application should be thrown away and rewritten, but as it usually goes - instead of rewriting it, we need to base something new on it. Recently, we decided to go the DomainDrivenDesign path. So -- anti corruption layer could be a solution for our problems. As far as I understand, this way it should be possible to gradually rewrite the old application. But -- I can't find any good example. I would appreciate ANY information. Troy Campano In my particular implementation, EmployeeAccessService is

My company has tons of legacy applications that are written in VB6. We are in transitions from moving VB6 applications to .NET (3.5 specifically). What would be the best strategy for moving form VB6 to .NET? NOTE : Below update should go to "Project Management" and has nothing to do with the main question. [UPDATE] : Thank you for your feedback so far Now there are more question that pop up are how would you assign developers to develop new applications? Should there be a special one-time upgrade division that will convert legacy apps to new ones? Or should every developer participate on

I'm currently working on a large and old C++ application that has had many developers before me. There is a lot of "dead code" in the project, classes and functions that aren't used by anyone anymore. What tools are available for C++ to make a analysis of large code base to detect and refactor dead code? Note: I'm not talking about test coverage tool like gcov. How do you find dead code in your project? Alan Jackson You'll want to use a static analysis tool StackOverflow: What open source C++ static analysis tools are available? StackOverflow: C++ static code analysis tool on Windows Wikipedia

There is an insightful question about reading a C/C++ data structure in C# from a byte array , but I cannot get the code to work for my collection of big-endian (network byte order) bytes. (EDIT: Note that my real struct has more than just one field.) Is there a way to marshal the bytes into a big-endian version of the structure and then pull out the values in the endianness of the framework (that of the host, which is usually little-endian)? (Note, reversing the array of bytes will not work - each value's bytes must be reversed, which does not give you the same collection as reversing all of