Re: D2007 vs MS Visual Studio 2005
I think we are confusing two things here: having the Visual Studio 2005
run on Vista, and producing applications that take advantage of the Vista's
new futures, such as WPF.
Now, there is the Visual Studio 2005 extensions for .NET Framework 3.0
(WCF & WPF), November 2006 CTP, but as far as I understand it is
not compatible with the Service Pack 1.
.
Relevant Pages
- Re: The New Roadmap
... > at where VS itself is standing on integrated WPF? ... You are certainly entitled to have your own opinion about the usefulness of the Cider WPF designer but I would like to know your creditable Microsoft source that said "in fact it's not supposed to work". ... But then Expression Designer already integrates into Visual Studio to provide a more capable two-way designer when when the limits of Cider are encountered. ... IDE a new WPF designer with functionality equivalent to Expression Blend and I guess from your comment that they "thus still have some time to get this right" you expect this to be done Real Soon Now. ... (borland.public.delphi.non-technical) - Re: Stand WPF
... Auch die Schwächen im Designer ... WPF erzeugt. ... [WPF Improvements in Visual Studio 2010 for Building Business Apps | Visual Studio Team Interviews | Channel 9] ... Dipl.Inf. Frank Dzaebel ... (microsoft.public.de.german.entwickler.dotnet.csharp) - WinFx: WPF Dynamically build UI
... I'm currently playing a little bit with the new wpf in Visual Studio 2005. ... was pretty excited about the posssibilities you have with XAML. ... (microsoft.public.dotnet.framework) - WinFX: Remoting with GUIs
... I'm currently playing a little bit with the new wpf in Visual Studio 2005. ... was pretty excited about the posssibilities you have with XAML. ... (microsoft.public.dotnet.framework.remoting) - Vs2008 SP1 problems
... vs would just crash silently with no error message. ... So I decided to remove both service packs. ... So I uninstalled visual studio and reinstalled. ... The error also occurs if any attempt is made to open an xaml file in the wpf ... (microsoft.public.vsnet.general) |
|