Tuesday, May 22, 2007

URL ReWriting with ASP.NET

Recently I got onto a nice article I want to share with you. It is about URL ReWriting with ASP.NET.
I am sure the Open Source manics of you know pretty good the "mod_rewrite" for Apache Web Server. But for those of you who are .NET maniacs, this article will be a good start: http://weblogs.asp.net/scottgu/archive/2007/02/26/tip-trick-url-rewriting-with-asp-net.aspx

Enjoy it!

Saturday, May 19, 2007

MSXML6 as Prerequisite for most of installations

I hate MSXML 6 !
When I run setup of some "Visual Studio 2005" family softwares I got the error "MSXML6 could not be install, setup cannot continue". Then, when I go to Control panel I see "MSXML6 Parser". If I try to UNINSTALL it says "This action can be ... only for installed components" ... What the ?
Then a veeeryyyy useful post comes to be the only one that helped:
Aaron Stebner's WebLog.
For fast issue - first try: setup.exe /NO_BSLN_CHECK
It works on almost every Visual Studio family products, but unfortunately it does not work on SQL Server family products ...
So another workaround should be found for the SQL Family.

Tuesday, May 8, 2007

More Object Datasource

Ever encounter "Exception Details: System.InvalidOperationException: ObjectDataSource 'ods' could not find a non-generic method 'Update' that has parameters: ...." ? No kidding ?
I will not show you the hot water, people have already found it :
http://geekswithblogs.net/mnf/archive/2007/03/01/107642.aspx (the short version)
http://weblogs.asp.net/bradygaster/archive/2006/09/26/How-to-Bloody-Your-Forehead.aspx (the long story)
Just a hint - do not use "Use Optimistic Concurrency" !!!
And then you Should slightly modify the Auto-generated code for the ODS.
Well, it's not a good idea at all to mess with auto-generated code, but what else can we do?
Luckily, Microsoft has promised that this BUG is fixed for the next release of Visual Studio.
I wander how many additional bugs are there waiting to crash developer's work ;)

Friday, May 4, 2007

ObjectDataSource ?

I want to give you a hint of something that bothered me the last hours:
The type specified in the TypeName property of ObjectDataSource '' could not be found.
This is the Error I was getting the last half an hour and that drove me crazy.
A simple definition lays behind in the code:

ObjectDataSource odsP = new ObjectDataSource();
odsP.TypeName = "OrderDoc";
odsP.SelectMethod = "GetPriceDetails";

Why then the message is with EMPTY TypeName ?
Well, if you have the definition of the OrderDoc in the scope (namespace) of your current project that is executing the code - there is no problem at all.
The problem comes out when you place your business logic in a business logic layer. And there is no matter how you add the reference to the BL project. You would never succeed.
The answer lays behind the mechanisim the ObjectDataSource is searching for the given TypeName. Well, it uses Reflection, so you must provide a fully-qualified name of the Type including the assembly / namespace. For example:
So the lines in the example will turn onto:

ObjectDataSource odsP = new ObjectDataSource();
odsP.TypeName = "MyBusinessLogic.OrdersLogic.OrderDoc";
odsP.SelectMethod = "GetPriceDetails";