Ooops... Just saw CodeProject's MSDN ad. The CodeProject ad in next month's points to codeRproject.com. ---------------------------- Wesner Moise http://wesnerm.blogs.com

The breakthrough development tools are necessary to accomplish what you are envisioning. Would you rather have programmers spend time tracing memory leaks or create the next big thing. We could all still be programming assembly, which would lead to faster programs, but I doubt that we would even have half of the features of the software we use currently, if that were the case. I am working on a cool software, which will take advantage of Moore's law, but it's only possible because the development effort is less onerous with the new development tools. Satisfy the developer before the user. Managed code is an enabler because it makes code easier to write, and cuts out all the low-level management of detail that hinders creativity and progress. ---------------------------- Wesner Moise http://wesnerm.blogs.com

Let's not :( I don't want to draw attention to myself every week. ---------------------------- Wesner Moise http://wesnerm.blogs.com

Saw your picture in your profile. You're a beauty. Us computer nerds have never seen a girl before. Watch out for us. :laugh: ---------------------------- Wesner Moise http://wesnerm.blogs.com

I used typepad.com, but I may eventually use my own package like .Text or something. ---------------------------- Wesner Moise http://wesnerm.blogs.com

Your family and your friends, if no one else, may find your life interesting... Thanks, Wes ---------------------------- Wesner Moise http://wesnerm.blogs.com/net\_undocumented/

I started a new blog. It's great fun; been posting an average of two articles a day, mostly tech/Microsoft related. Now, I feel like somebody! ---------------------------- Wesner Moise http://wesnerm.blogs.com/net_undocumented/

Google is my one-stop shop for everything... Whew... ---------------------------- Wesner Moise http://wesnerm.blogs.com/net\_undocumented/

I should be easy for you to become an American citizen. There's still time. ---------------------------- Wesner Moise http://wesnerm.blogs.com/net\_undocumented/

:) ---------------------------- Wesner Moise

Most of the Office (Excel, Word) applications are written in C with MS extensions. They are so old--older than C++, as is most of Windows. The shared Office stuff is in C++. Powerpoint is in MFC/C++; I guess Visio and Project are too. Basically, all the new stuff is in MFC, rather than written from the ground up. Why rebuild the infrastructure when it's already there. Now I think people are moving to managed code. You can tell just by looking at what dlls each application links to. The new apps, like IE and .NET/CLR, tend to use the latest techniques. Nowadays, there is a serious effort across the company to use the most rigorous and advanced practices. They tossed away Window 9X crap; they are redoing everything. Their build process is so advanced now, and you have to pass layers of tests--breadth tests, style tests, advanced error detections and security tests--for a check-in to pass. Microsoft has matured a lot since I left four-years ago. ---------------------------- Wesner Moise

If that is what you want, look at the Avalon sessions. "Avalon": Building Applications with Controls and Dialogs Track: Client Code: CLI300 Speakers: Rob Relyea Learn the way to build basic "Avalon"-based applications. This session covers layout of applications, dialogs and controls using markup, code, properties, methods, events and basic animations. ---------------------------- Wesner Moise

Refactoring is a feature that you see in other IDEs of rewriting code for better maintenance and reuse. Look up google. ---------------------------- Wesner Moise

Infinite loop... ---------------------------- Wesner Moise

great, I am doing my 200th post!! ---------------------------- Wesner Moise

at http://mymsevents.com/MyMSEvents/Search.aspx[^] The abstracts to each of the PDC sessions are available and offer more clues to new features of the OS. I have known about these features for awhile, but couldn't say anything because of NDA, but now that Microsoft has disclosed them. I'm telling you, this year's PDC is going to ROCK!!!!! For example, "refactoring" and "visualization" is mentioned as a new feature in the C# session. The C++ session mentions "deterministic finalization." Visual C# "Whidbey": IDE Enhancements for the C# Developer Track: Tools and Languages Code: TLS321 Speakers: Anson Horton, Joe Nalewabau Visual C# "Whidbey" includes improvements to the code editor and debugger that cater to the code-focused needs of the C# developer. With support for refactoring in the code editor, advanced visualizations in the debugger, and more, Visual C# "Whidbey" supplements its modern syntax and component-oriented features with new and powerful productivity-enhancing IDE features. Also, check out the section on Windows Forms with Office-style controls. Windows Forms: Building Polished Applications with the .NET Framework "Whidbey" Track: Client Code: CLI331 Speakers: Mark Rideout Learn about the new "Whidbey" Windows Forms features that enable you to build Office-style, professional looking, cutting-edge applications and user interfaces. Learn how to use the new toolbar control to make cool, rich toolbars and menus that behave and look just like Office. Next, integrate in the GridView, WebBrowser, and ActiveDocument controls to provide rich content. Finally, add dynamic application update checks to ensure your users have the latest and greatest! There's lots more... Read up on Avalon, Indigo, Yukon and Longhorn... Thanks, Wes ---------------------------- Wesner Moise

Peasle spot it now. Wes ---------------------------- Wesner Moise

I am under NDA, so I can't mention codenames, but it looks like some (soon to be ex-?)Microsoft guys have already posted some slides on publicly available info about future MS products. I won't acknowledge if the info is true or not. http://radio.weblogs.com/0117167/2003/08/29.html#a439 Thanks, Wes

A number of years ago Microsoft published the DefWndProc source code, which is what you call from your WndProc after you have processed a windows message. I believe the function was over 3000 lines of code, although I have seen such long switches in Excel functions, too, but maybe not that long. There was a label called "ICantBelieveIUsedGoto" in the function, that went from one location of the function to another location. What I don't understand is why each case could have been broken out into a separate function, thus making it easier to maintain. Oh, yes, I remember, because this was windows 3.1. Thanks, Wes

I would not categorize #1 as a bug... Find and Replace did not have to offer "Selection only" in the first place; most products don't. Secondly, the act of performing "Find" causes the selection to be changed. Understandably, there are conflicts between maintaining the current selection and actually using the selection to indicate the text found. What's the proper way of dealing with this type of feature? 1) Saving the old selection, which also needs to track the selection accross edits and replacements. Then search for the selected text. Then when the user has finish searching, restore the selection. This is too complex and requires additional state for marginal gain. 2) Lost the current selection. But this is the same as doing find with cursor positioned at the start of the selection. 3) Punt on the feature. Disallow find all and replace all. Instead of drilling down infinitely on an obscure feature, focus on the feature set that most people everyone cares about. Also there is an simple, straightforward, effective and just as convenient work around, moving the cursor to the start of the area that you care about searching and doing find next or replace next. The Microsoft developers were trying to provide as the "selection only" feature for specifying an area constraint to "Replace All", which does not have as convenient a workaround. Remember, "Replace All" applies to everything. Bug 2 is probably caused by conflicts due "Find within HTML". This is hardly a bug. BTW: My article "Win32 Library" didn't show up in the July survey, and it is rated higher than at least one of the articles listed. Thanks, Wes Moise