Everyone on the VC team is getting really excited about the upcoming PDC in Los Angeles. This will be our first chance to show you some of our upcoming features and a great way for us to get feedback direct from you on what we have implemented so far and what we have planned. PDCs are always one of our most exciting events to speak at, given the forward looking nature of the program (and, to be truthful, we learn as much about what other teams are planning as attendees do sometimes!) Just wanted to add a small reminder that VC will be presenting two sessions at the PDC and invite any of you who will be there to drop by and meet us. The two sessions are:
· Microsoft Visual C++: 10 Is the New 6, presented by Boris Jabes.
· Microsoft Visual Studio: Building Applications with MFC, presented by myself.
Also attending from VC will be Arjun Bijanki and Raman Sharma; all four of us will be delighted to meet you during the event, at one of the above sessions or look for us in the lounge too. Once we have our lounge sessions booked we will post the times here, if you would like to arrange to meet.
Funny, how the moaners and whiners come out loud no matter what you do.
As Microsoft started to improve the C++ compiler and library the IDE moaners came out ranting how much better VC6 was.
Now Microsoft tells us that they listened and want to bring back the good VC6 feeling the other whiners come out to tell us how bad VC6 was.
Just like WinXP moaners telling us that MacOS is so much cooler and the Vista whiners telling us they don't need any of those 3D GUI stuff.
That looks so childish to me. To the moaners out there: how about getting perfect yourself before telling others to be perfect.
Well, I am pretty excited how VS (for me mostly VC++ and a bit of C#) evolves and I like being able to choose a proper tool fitting the problem.
Keep on the good work!
As I know the standard is almost complete after September meeting and some compiler like GCC start to experimenting it or at least implementing some of it's features.
I really can't wait to see it in VC++.
While it might seem sad to say, DevStudio6 was the pinnacle of Microsoft C++ IDE.
All we wanted out of DevStudio were a few incremental IDE things:
More IDE standardization between VB and VC. Placing buttons on a form should have been universal. Equivalent toolbar layouts.
A NOT COM-language addon to VB so regular C++ classes could be easily imported into VB "classes" - thus making the fantasy of Developing the business layer in C/C++ and the GUI in VB closre to a reality.
The ability for the VC IDE Designer to make arrays of controls like in VB.
The ability for the VC IDE Designer to embed controls in panels in an Object Oriented way like in VB
The ability for VC to make modeless dialogs much more straightforward.
And of course for Microsoft to flush out support for ATL/COM so that we could use move from MFC to ATL/COM like they wanted us to in 1998 - but they suddenly became too busy migrating us to .Net 1.0 - I mean .Net 1.1 - I mean .Net 2.0 - I mean WinForms - I mean XML - I mean XAML - I mean WPF - I mean Ribbons...
As I know the standard has been almost completed after September meeting and some compiler like GCC started to experimenting it or at least implementing some of it's features.
well said rbiro!
But don't forget the extreme busy-ness and focus on .Net 3.0, .NET 3.5, .NET 4.0, CLR, Interop, CLI.
> More IDE standardization between VB and VC.
> Placing buttons on a form should have been
> universal. Equivalent toolbar layouts.
That was started with VS.Net. But at the beginning you will loose functionality as you cannot do everything at once.
> A NOT COM-language addon to VB so regular
> C++ classes could be easily imported into
> VB "classes"
How should that work without COM? There is no binary standard for the layout of C++ classes. So using COM with its vtable layout and IUnknown for lifetime managment (AddRef/Release) and dynamic casting (QueryInterface) is just the solution as this is the only binary standard you have. And using interfaces helps to get versioning right. Doing that with any C++ class hierarchie which you enhance over time would be challenging.
And what about template classes. Is template exporting implemented by C++ compilers?
> thus making the fantasy of Developing the
> business layer in C/C++ and the GUI in
> VB closre to a reality.
That is the whole point of XAML and stuff like the Expression tools.
I agree that WinForms did not make sense. It felt so wrong to get all the GUI layout stuff added in source code stuff and avoiding GUI resources like good old rc files.
But I guess that again was just a problem of timing and not being ready to ship the real thing which was designed to separate devs and designers: XAML
> The ability for the VC IDE Designer to
> embed controls in panels in an Object
> Oriented way like in VB
You call it OO others would call it RAD. Not everything which you can grab and drag around is object oriented ;-)
> And of course for Microsoft to flush out
> support for ATL/COM
Sorry, I am not a native speaker. What does flush out mean? Is it enhance support or drop support?
> Net 1.0 - I mean .Net 1.1 - I mean .Net 2.0
> I mean WinForms
I don't like WinForms either
> I mean XML
First class XML support is essential. Unfortunately XSLT 2.0 and XQuery will only be added to the managed world. MSXML stays where it is.
> I mean XAML - I mean WPF
Which is the same
> I mean Ribbons...
Which is wonderful for us devs and in Office it has a native COM interface and is so much better to develop with than command bars. So much control with callback events. You should try it, it is really a good thing!
I didn't look much at the Feature Pack as we use a different VC++ control vendor (codejock) but if they offer the same Ribbon support than the Office implementation gives you, it should be really nice to use.
> Sorry, I am not a native speaker. What does flush out mean? Is it enhance support or drop support?
From the context, it appears that "flesh out" was intended, meaning "enhance support".
A native XML based GUI layer is really missing in MFC.
> A native XML based GUI layer is really missing in MFC.
Almost agree with you. I hate *.rc!!!
But first VC++ needs a good, reliable and standard look (maybe a template based) XML library.
Nowadays we can see XML almost everywhere in software world, but Unfortunately there is no XML classes in the c++ standard library and worse is there won't be any in c++09.
Hopefully this focus on the IDE means that they will be taking care of all of the productivity things that they've removed or broken ("By Design"/"Won't Fix") from the IDE since 6.0.
Using a dropdown combobox instead of a checkbox for Yes/No options in the resource editor.
Removal of the "match case", "match whole word", and "use regular expression" toolbar buttons. (105507)
Making the search tool randomly switch to "selection" instead of "Current document" when doing an incremental search. (105673)
Disabling the standard F4 to open combobox dropdown in the search dialog. (374703)
Simple column select mode replaced with separate navigation functions for extending the selection as a column. (139752/108814)
Changed column select text on a single line and paste puts cursor at the end of the pasted selection instead of the beginning.
Removed ability to change language and tab settings for an individual file loaded in the IDE. (105749)
I would like to see a redesign of the .vcproj system to be more 'progammable' like makefiles, and less raw-data-ish.
Hello After my recent post on VC at the PDC I had a number of people ask me which PDC sessions I would
Can we read the manuscript of "Microsoft Visual C++: 10 is the new 6" after PDC?
It's so funny to see a lot of people complaining about v6. Actually it was better than any newer versions of VC comparing to it's timeline.