At the same time I disagree
because there are places where windows forms controls for examples, which
are part of the framework, contain code that is used only to support the
design time. Idealy the design time code is isolated in a separate dll, but
in practice this is not always posible. This design time feature may not
only be used in VS. Any application can host a designer - example is
SharpDevelop IDE. If there is a bug in this code it will show up in VS at
design time, but I'd consider this as a bug in the framework.
Ok, here I fully agree with you. But such bugs are not often discussed
(if you would make statistics over all the questions here in the
newsgroup and compare them with talks like "I use VS.NET" - "OK fine,
which version of the .NET Framework" - "2003").
Maybe it's Microsoft's fault, who give away the IDE and build in
anything into it. I would prefer a more divided way, a IDE and the
Framework. Then ridiculous things as the need of 2 IDEs for 2 different
..NET Framework version would stop... that's just one of the main reasons
for me NOT to use VS.NET.
.... before getting too philosophical...
bye
Markus