Re: .NET 3.0

I.P. Nichols wrote:
http://blogs.msdn.com/jnak/archive/2006/08/15/700295.aspx
"Will Visual Studio's WPF Designer be available as a reusable component outside of Visual Studio, like the Windows Forms designer is?" - And his answer is a no! Sounds like déjà vu all over again ;-)



"The WPF Designer has been architected from the ground up to provide many levels of reuse, from building blocks to reusing the designer itself, and we foresee having this functionality in future versions of Visual Studio."


the answer sounds more like "probably in the future" as opposed to just "no!"
.

Relevant Pages

  • Re: vista avalon etc.
    ... But we do work fine with Cider, the WPF designer in Visual Studio. ... Our project files are MSBuild, of course, so it /could/ be that Sparkle will just take em without questions - it could on the other hand also be that Sparkle makes some assumptions about the project being C# or VB - wouldn't be the first time - and needs an integration package from us at some time, to enable full support. ...
    (borland.public.delphi.non-technical)
  • Re: .NET 3.0
    ... made sense to only include the WPF designer with Visual Studio rather ... The WPF Designer can't currently be included in the framework if no other ... for the end user support as to make it hostable but that's my just my own ...
    (borland.public.delphi.non-technical)
  • Re: Turbo questions
    ... not be available as a reusable component outside of Visual Studio ... "The WPF Designer has been architected from the ground up to provide ... Architecting ... The best way to bug Borland about bugs. ...
    (borland.public.delphi.non-technical)