Jelle Druyts .NET Consultant
Just another ignorant weirdo from Antwerp, Belgium trying to make sense out of it all
Nice: now you get a task-switch window if you press CTRL-TAB to switch between your windows too (a bit like ALT-TAB in Windows itself) with the available windows and the active tools (like the Solution Explorer).
It seems they have already fixed the minor F2 usability bug. How thoughtful "Make" is still there though, although they moved it into the "Build" menu. Not good enough, and certainly not as long as CTRL-SHIFT-B doesn't 'Make' by default. Can't seem to assign another shortcut to it either, apparently...
The removed all WinBar stuff in this build (office style toolbar), I wasn't too fond of the implementation yet but why they ripped it out altogether...? Ah well, it'll be back I guess, they've been marketing it already so there's no way back.
Ah the DataGridView (formerly known as GridView) is already looking much better. It's like the ASP.NET DataGrid we all got to know and love Sorting, header resizing, flexible column types, extensive support for formatting and templates, now in a Windows Forms environment. Cool!
The StatusBar control has been replaced by a StatusStrip, which now finally supports a ProgressBar. It will probably support more things later on too (like buttons and such). Well it's a start but I'd rather see it able to support any type of control. (I wrote a class once that could handle that actually...)
Hey another code generator (the "Strongly Typed Resource Builder") has entered the building! Resource files are now backed by typed classes so you can go form.Text = AppWideResources.ApplicationTitle if you have a resource key called "ApplicationTitle" in an AppWideResources.resx file. The resource editor has also undergone a remake (thank God, because quite frankly: it sucked): now you can add images, icons, audio, files, ... from the IDE. Pretty nice! Sorry for Lutz Roeder's Resourcer though
form.Text = AppWideResources.ApplicationTitle
Damn. The WebBrowser component seems broken in this build: I get a COM error Uhm yeah what else, I really didn't expect it all to be managed code by now
And in general, the Windows Forms designer is really messing with my head. It keeps messing up the generated code and it just seems a lot less stable than the PDC build. Well can't have it all I guess...