Actually one can host the .Net designer in an application. It is rather
complicated and not well documented, at least as of VS2003. I hosted the
..Net 1.1 design time in an application, but I learned it through an online
example. It involved implementing many interfaces and seemed a bit half
baked, at least as a library that was meant for use in other applications.
My guess is that it was designed for VisualStudio, but then exposed to the
public as an afterthought. I haven't tried it in later versions. For what I
needed to do at the time it was great, I just wish it was a bit more
designed as a general purpose component.
"Ben Voigt [C++ MVP]" <rb*@nospam.nospamwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...
Andre Kaufmann wrote:
>Ben Voigt [C++ MVP] wrote:
>>Giovanni Dicanio wrote:
"Kenneth Porter" <sh*************@sewingwitch.comha scritto nel
messaggio news:Xn**************************@207.46.248.16...
[...]
C# doesn't have. Visual Studio has, in the Forms Designer, a RAD
I think the WinForms designer is part of the .NET framework and can be
hosted in other applications too.
The .NET framework includes support for including design-time support for
user controls, but not the design environment itself. I think the design
environment can be hosted, but you'd be using the Visual Studio
extensibility SDK and licensing Visual Studio runtime components, not just
the .NET framework.
>>
>>environment which is rather prone to crashing (i.e. less than "very
good").
The C++ one is quite bad but I don't have that impression regarding
the C# (managed languages) one.
I've had the C# designer (VS2005) crash numerous times. The fact that the
crash dialog for Visual Studio isn't actually modal (a serendipitous bug I
suspect) is the only thing that's saved by solution from total uselessness
on multiple occasions (i.e. I was able to close the faulting designer
window and save the solution before letting the crash window exit Visual
Studio, otherwise merely opening the solution produced a crash)
>>
>>[...]
Andre