Lasse Eskildsen - All Comments

re: The asp.net attribute

codedefiner — Thu, 30 Jul 2009 14:54:53 GMT

good article

you can find some information about Asp.net Deployment at

<a href="www.codedefiner.com/.../aspnetDeployement.aspx">Deployment of Asp.Net website</a>

re: The asp.net attribute

ravi — Sun, 07 Jun 2009 17:52:34 GMT

can u mention abt unnecessary files to be excluded ....

links for 2009-04-29 « dstelow notes…

links for 2009-04-29 « dstelow notes… — Thu, 30 Apr 2009 00:31:00 GMT

Pingback from links for 2009-04-29 « dstelow notes…

re: Performance Profiling And Commerce Server 2007

lasseeskildsen — Tue, 14 Apr 2009 19:48:21 GMT

Do you mean the GetCatalog method? I didn't find a workaround, other than caching the catalog. However, since this post, we have switched to a DDD approach as an anti corruption layer, so we map all Commerce Server entities to POCO classes which we put in our own cache. This has resulted in a major performance increase.

re: Performance Profiling And Commerce Server 2007

Bob — Thu, 09 Apr 2009 19:27:11 GMT

Where you able to work around the CS API performance problem? I have the same issue as we cache everything we can this API call is showing up as the bottleneck.

re: Demystifying the Page_Load Method

lasseeskildsen — Sun, 23 Nov 2008 23:38:31 GMT

First off, I really appreciate you guy's opinions.

I usually use the override approach, but I have two concerns on this one:

- The purpose of e.g. OnLoad should be to raise the Load-event.

- Overriding the method implies you want to change the method's behavior.

Ideally, I would not add any business logic to the OnLoad method. Say for instance I inherit page into MyPage, overrides OnLoad, inherits MyPage and overrides OnLoad. This way I cannot raise the Load event without triggering the logic added to the OnLoad method. This can be perfectly ok, but if I want to avoid this, the Page_Load approach can be used.

I'm not saying that either one is right or wrong, just that is has different usages, e.g. to avoid those nasty state variables.

Thoughts?

re: Demystifying the Page_Load Method

Soren — Sun, 23 Nov 2008 10:25:00 GMT

Great post.nice to get an expanstion on why it worked.

re: Demystifying the Page_Load Method

Dennis Riis — Fri, 21 Nov 2008 22:38:29 GMT

I am with Peter on this one. The problem with using a Page_Load method, is the fact that it is somehow "magic". It is not apparent why it gets called, in fact you just spent an entire blog post entire blog post explaining why. I'm in favour of overriding the appropiate methods (and you still get to decide when base.OnXxx is called, mind you) at all times.

I think overriding a method promotes OO design and thinking, since the principle will work in whatever environment you might find yourself in, while these "magic" method names will only work in ASP .NET when writing code that inherits TemplateControl.

re: Demystifying the Page_Load Method

lasseeskildsen — Fri, 21 Nov 2008 07:25:03 GMT

Yes, you're right about it takes a lot more explaining. In addition, Page_Load is called after base.OnLoad, so if you want to do some stuff before that, overriding the OnLoad can be the way to go.

re: Demystifying the Page_Load Method

Peter — Thu, 20 Nov 2008 23:31:23 GMT

" from now on I don't see any reason why not to use them"

Here's a reason, how many words do you need to explain how it works as opposed to explaining the override method. Using the override makes far more sense, it's part of the language and OOP. It doesn't give you this impression that you're living on a cloud. The code you write behind the aspx is actually a class that inherits from a different class. The Page_Load method is an abomination of object oriented design. It introduced a lot of confusion. What if you override OnLoad and use Page_Load at the same time, which one gets called first and why? If you have to fire up VS to test it out you've already proven my point.