I agree with David, This is a type of problem that transcends any Particular IDE ( I can not prove this formally but just a conjecture at this point).
The solution is to use Builder Pattern and move away from visual inheritence within the IDE. By doing so the porblem can be shifted from IDE domain to programmer domain where one has full control over all the details. If anyone is aware of a situation that Builder Pattern can not handle please let me know. Regards Arjang On 27 April 2010 08:43, David Richards <[email protected]> wrote: > Greg, I'll preface my response by saying the following is all in a > windows mobile environment. > > In my experience, any kind of inheritance in a form has a very high > chance of causing this and other problems. At least this problem is > better than the one where it all seems to work ok but secretly, the > designer has modified your code so the form doesn't work properly any > more and you don't discover it until it gets to the client. > > Once you do anything "tricky" in the form, the designer can't handle > it any more and you have to stop using it. Either that or you have to > have two sets of code. One where the "tricky" stuff is commented out > just so you can use the designer, the other where the "tricky" stuff > is back in for release. > > I rarely do forms in the full framework so I'm not sure if it has > these same problems. > > David > > "If we can hit that bullseye, the rest of the dominoes > will fall like a house of cards... checkmate!" > -Zapp Brannigan, Futurama > > > > > On Mon, Apr 26, 2010 at 12:19, Greg Keogh <[email protected]> wrote: >> I started work this morning on a Forms utility project that I’ve been >> working on for several weeks. There are a dozen controls derived from a >> simple “base UserControl” full of helper methods. I have found that every >> control derived directly or indirectly from the base control cannot be >> opened in the designer. Visual Studio 2008 crashes with the “encountered a >> problem and needs to close” prompt. >> >> >> >> Attaching a second VS2008 instance to trap the problem doesn’t work. The >> crash is not trappable. >> >> >> >> I have deleted and recreated the base control with different names, I have >> restored backup copies, I have commented out all code in the base classes at >> different levels. Nothing makes any difference to the designer crash. >> >> >> >> The only thing left to do now is recreate the solution and project and >> slowly recreate each control and paste the original code back in until it >> either works or I might luckily find the point at which it starts to crash. >> This could take about 4-5 hours and the outcome is uncertain. It looks like >> my whole day of development is ruined. >> >> >> >> I just thought I’d mention this problem in case someone else has been >> through it and has any ideas. >> >> >> >> Greg >> >> >
