Palladino wrote: Dammit! Yeah, I had the same reaction the first time I wanted to use it, some time about two years ago. I dislike large function bodies, but realistically there are a number of situation-specific algorithms that depend on a long sequence of unrepeated operations. To reduce the size, one is left with the option of breaking them into smaller chunks as subroutines, then calling each subroutine in sequence. I've seen differences in how well that approach works when maintenance is being performed by novices to the software. I've seen genuinely intense frustration expressed by some developers when they have to nest down through two or more levels of subroutine that were simply put in to eliminate very lengthy code sequences, where the developer in question felt it would have been much easier to follow the sequence in its original lengthy form. Allowing collapsible regions within a subroutine brings the best of both techniques to bear on the problem.

I have no idea what StarTeam is, but really what you want to do is branch your code base every time you do a release. Then you keep working on the branched copy, but you have a freeze of the version that's in the field. As for distribution. I use 'Advanced Installer' and it rocks, well worth the price of admission ( only $100 or so ). www.advancedinstaller.com[^] The bit that I always find a hassle is the database scripts. I don't know what other people do, but I long ago wrote an app that has a database connection string in the config file, and that scours a subdirectory for .sql files and executes them. When I distribute an app with a database, I install a named instance of MSDE, which makes it easier to set up the installer app to find it to run scripts against it ( that is, I know what I am looking for ). Christian Graus - Microsoft MVP - C++

Daniel Turini wrote: Since they're using Java, probably they're still waiting for the application to finish loading. :laugh::laugh::laugh: Excellent! :-D Microsoft MVP, Visual C# My Articles

I must have read 'Life is beautiful' at least 5 times.

Hi again, Marc! Now I have the clearest subject in my mind. I want assemblies obsfucation but it would like the names of the members not to be altered by this process. That is possible? Sincerely, Marcelo Palladino Brazil

A control and a window are distinct window classes with different window styles. Instead of having to modify window styles and going to the work of implementing a pump, simply host the control in a borderless form and return the dialog result from the form: public static DialogResult Load(MyFakeWindow window) { Form f = new Form(); f.FormBorderStyle = FormBorderStyle.None; f.Controls.Add(window); window.Dock = DockStyle.Fill;   DialogResult result = f.ShowDialog(); f.Dispose();   return result; } -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

Michael, I don't have as thanking for this "chat" that we had. For this first moment it is everything OK, thank you very much (really)! With relationship to the Ingo book´s, I tried to buy for here but I didn't get (still)... It was worth, Marcelo Palladino Brazil

Thanks, Brian. He's much better now, and, with some luck, only two more days and everything will be normal again. We spent the last 10 days at the hospital, because what started like a simple, easy pneumonia was actually a very strong, resistant pneumonia that got his two lumbs. Trying to make bits uncopyable is like trying to make water not wet. -- Bruce Schneier By the way, dog_spawn isn't a nickname - it is my name with an underscore instead of a space. -- dog_spawn