Blog Home  Home Feed your aggregator (RSS 2.0)  
Microsoft .NET Framework 3.0, Design time stuff and more - Manuel Abadia's ASP.NET stuff
 
# Monday, 19 June 2006

First I have to apologize for not posting anything in nearly two weeks, but a lot of things have happened lately: I did a quick work (a week) for Namco Mobile; I have been two days in bed with temperature; I did a Reiki first degree course; too much work in the last days and a lot more to come until august…

I read somewhere that Microsoft .NET Framework 3.0 will be released at the end of the year. Even if it is not a complete change of the .NET Framework 2.0 and can be seen as .NET Framework 2.0 + Windows Presentation Foundation (WPF) + Windows Communication Foundation (WCF) + Windows Workflow Foundation (WF) + Windows CardSpace (WCS) it is kind of a pain to be learning version 2.0 and have a new release before mastering .NET Framework 2.0. If you add Atlas to the mix the conclusion is: “Too many things to learn and no time to do it!”. I hope we can live with .NET Framework 3.0 for a few years.

I don’t know what happens in other cities/countries but most of the companies here are still using .NET 1.x and probably a lot of them will still be using it when .NET 3.0 is released…

Talking about other things, I have started to add full design time support to the ExtendedObjectDataSource package and this is what I have at the moment:

Design time wizard

Design time wizard


As you can see I have added more options that are not present in the standard ObjectDataSource like being able to configure paging in the wizard and also being able to choose also the SelectCountMethod (for the CompatObjectDataSource. The ExtendedObjectDataSource can extract the total row count in the SelectMethod).

If somebody misses something in the wizard let me know ASAP so I can think of including it.

Every time I have to use Winforms I really hate the poor control set that is available (at least in version 2.0 you have a menu that does not look like it was made for windows 95 :-P). I can’t believe that the framework didn’t ship with a wizard control so I had to waste my time coding one.

To finish this post, I’ll tell you a cool tip to debug design time stuff. Forget everything that you did to set up the project to debug design time classes. You’ll have a debugger attached to the current Visual Studio instance and awaiting your orders if you add this line of code where you want the debugger to show up:

System.Diagnostics.Debugger.Launch();

Monday, 19 June 2006 00:49:35 (Romance Daylight Time, UTC+02:00)  #    Comments [1]   ASP.NET | General | Microsoft .NET Framework  | 
Copyright © 2018 Manuel Abadia. All rights reserved.
DasBlog 'Portal' theme by Johnny Hughes.