New answers tagged

0

Generally speaking, you don't usually do a calculation for a salaried employee. You usually have a field to hold the salary amount that was pre-calculated for the number of pay periods in a year. Some payroll systems have you enter the employees salary for the entire year and it makes the per payroll calculation based on the number of pay periods. Handling ...


2

If you map different menu items to the same function with different parameters different functions within the same class different classes within the same assembly, having a standard entry function different DLLs, each having a standard entry point defined by a special interface different executables, each having standard command line parameters is ...


0

Ignoring the issues you have in your team, it seem that the first one to address is to debug the code matching what is in production. Otherwise you might be chasing a bug that was already fixed in the code you have in your "Source control". As this is .NET you could easily "decompile" the production binaries to compare the code with what you have. It's not ...


0

I would say (5) is the one you need to fix first. If you don't know which code is running in production, you have no safe way of reproducing and fixing problems. This makes any other change you introduce dangerous, since it might cause problems you cannot foresee and cannot reproduce. You may need to do some detective work and perhaps reverse engineering to ...


4

First, all the above... ditto. Some heuristics: Use source control on your development computer. It's the best thing I've done. It is not a substitute for the project's version control, which we have. It's a tool that gives amazing freedom to fearlessly experiment, hack, work problems simultaneously yet independently, etc. I am better at using version ...


5

Start with logging. This will have the greatest impact. Implement a logging framework into the code base, like Log4Net or similar. Start logging what the code does. Debugging should be possible locally. If not, work on getting the symbol files (PDBs) so you can debug into 3rd party dlls to gain a complete picture of the issues that are occurring. Tools ...


8

1) Debugger cannot be used on client site ... That's perfectly normal. ... or locally Now that's a problem. 2) There is virtually no logging done in our apps. Logging is the Production Debugging. There are no unit tests. Oh dear. All to common, though. 3) Version control only has 1 version of the full solution Then you're ...


21

Robert Harvey's advice is likely best, but since career advice is off topic, I'll give what answer can be given: You are at the bottom of a very steep mountain covered in brambles and mud and irritable mountain goats. There's no easy way up. If you want to get to the top, you've got to force your way up one tremendously painful step at a time. It seems ...



Top 50 recent answers are included