Application Lifecycle

In the end it was a mix of a to small sample for calculating the relative variance and some unnecessary processes (upgrade service for ex.) Now with the bigger sample and the stopped processes the results are more consistent. Thank you for your help. Regards Sascha

DoorOs ? Regards Sascha

The sensible advantages supplied by marketing handbags can improve your business in number of interesting ways. When the body from the marketing [url=http://www.marcbymarcsale.com/marc-by-marc-jacobs-clothing.html\]Marc Jacobs Sale[/url] selected by your small business is thick, then you'll get enough space to create 4-5 lines of significant info on the Discount Designer Bags pocket handbags.You will find various suppliers on the web that provide personalized marketing handbags. The option ranges from lightweight handbags,[url=http://www.marcbymarcsale.com/marc-jacobs-purses.html/\]http://www.marcbymarcsale.com/marc-jacobs-purses.html/\[/url\] small design printed handbags, custom printed handbags and much more with variety Good Handbags design and print. These web based providers will require your message and print it on your preferred handbags at an affordable cost. So for additional info on printed marketing handbags, advertising and marketing products and items browse the top providers online today.

tomas.ivan wrote: there was a project (A), whose output is mixture of exe and dll files. tomas.ivan wrote: The dll files are not in source control, however there is a possibility to build them. Either those two statements are mutually exclusive or you think that the dlls need to be in source control after the build complete. For the second part the dlls need no more been in source control than the install executable is. Ignoring that and looking at a high level view then... A configuration management (CM) person is a person whose job or at least a principle role is to do builds. And only do builds (the role.) And given the following two possibilities. A - Two solutions. One used only be developers. Second that includes projects of first solutions in addition to install shield. B - One solution. Includes common developer projects and InstallShield. With a CM person/role then use A. If not then B. Might keep in mind that InstallShield licenses, specifically cost, might require at least a CM role (versus every developer managing InstallShield.)

Thanks Shameel. I was hoping that would be the case. I've now set it to use whatever the user has set as their system default, as the initial font.

Remove this crappy add!

You covered some good points here, I think a meaningful response is very important for comments. Plumbing Billerica Plumbing West palm beach Roofing West Palm Beach Roofing Fort Lauderdale

In a previous life, we had one system (as in "app", but it was mainframes not PCs). Three copies - dev, test, prod. (Oh, and test was hot standby for prod. Testers knew that their system could disappear at the drop of a hat if prod hardware chucked a wobbly.) All worked fine until a second system was brought in (which of course had to interface with the first one). After a while, it became obvious that we needed another test copy of each system. Basically, to test a change for system A (which is going in as an isolated change, not a big-bang upgrade), you need a clone of system B prod. This is different from B test, where the B testers are playing with new stuff which will go into B prod down the track. We wound up combining that integration testing function with user training, which wasn't ideal but did save the odd megabuck's worth of big iron. Just my two bob. Peter Software rusts. Simon Stephenson, ca 1994.

There is no general purpose easy way to do everything. It is possible, but difficult, to use code insertion techniques to simulate any error. At best, and at the most complicated, you actually modify the code at run time to force an error. Some people suggest using interfaces. These are outside those required by the design but are put in place solely to support testing. The problem with that is that not everything is solved with that and it might require a lot of interfaces. One can also be creative about testing. For example if I need to test connectivity problems I can use a system call, in the test code, to drop my IP (of course I better restore it as well.) Or I can stop SQL Server pro grammatically when doing database error tests (again make sure to restart it.)

Hey guy, United ahead electronics.,ltd here, selling IC PARTS with good quality and low price. contact me by eamil:diana@united-ahead-electronics.com

Good message.. 5 for that.

Thank you for suggestion. Goran

Have a look here http://www.codeguru.com/forum/showthread.php?t=327982

We have a well defined lifecycle, which we follow with a messianic zeal, except for those times when we don't or can't be bothered or the timescale is too tight and the money too good, but apart from that we never deviate. It's pointless waiting till the end of the project to determine whether or not the lifecycle is actually working. We have quality gates at several key points in the process that we use to determine the actual usefulness of the process to the particular project. There is no, one size fits all, process that we can actually use as we tend to have to fit in with the way the clients work, so while we can agree up front on things such as maintenance releases, release schedules, beta drops, inphase documentation and the likes, other parts have to be fluid and we cope as we see fit. "WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes. My blog | My articles | MoXAML PowerToys | Onyx

Errr yes, in fact I do. But why ask that here? LinkedIn[^] | Blog[^] | Twitter[^]