Any other insightful comments, SmartiKat?
Obviously, since it doesn't happen in your "massive"
solution, it must not happen anywhere, right?
And, no duh, without a reproducible test case things are
more difficult to debug. But as I and others posting have
commented, this is not repeatable. It occurs frequently
enough; however, that someone even at Microsoft must have
experienced it, and based on the behavior they may have
been able to tune into the real problem.
In my opinion only a "rookie" programmer has never had to
deal with debugging a problem without a test case.
Is this what you tell your customers - "can't fix it
without a test case, sorry"
How unprofessional is that, rookie?
>you know... if you don't see a lot of users having the
same problem here,
>it might just be your system, Video driver, Maybe?
>One suggestion, call MS Tech support.
>One observation, any Rookie programmer knows that if you
can't reproduce the
>problem, you can't fix it.
>And finally, I do have a Solution that has both C#, VB,
and a lot of my own
>Custom Controls (both Windows Form and WebForm). The
totally number of
>projects in this solution is 34. So, I would think that
>significant work under it. And I have not seen this
problem you described.
>> Anyone who has done any significant work using many
>> projects in a single solution with several .NET control
>> projects knows what I am talking about - one of the
>> bugs in .NET (or any development environment, for that
>> matter). Compile time failures of intermediate control
>> projects can make controls "dissappear" on forms that
>> are placed on.
>> I can't believe the newsgroups aren't swamped with this
>> issue. Every serious .NET developer I have talked to in
>> area (Mpls) routinely hits this problem. If I don't
>> my eyes open for this at all times, I can easily waste
>> several hours a month on this problem.
>> Is anyone else fed up with this issue?
>> Don't ask me to post a reliable example here, because I
>> can't. It is sporadic but fairly frequent on large
>> solutions (i.e. > 20 projects with a significant number
>> controls). However, if Microsoft itself has done
>> any "real" work with its solutions and .NET controls,
>> HAD to see this problem. I am absolutely positive it is
>> not something freakish about my solution, since as I
>> everyone I talk to seems to hit the same issue.