Alexey Zakharov's Blog - All Comments

re: IRepository interface.

brainbox — Thu, 19 Nov 2009 18:08:59 GMT

Typical UoW implementation are usually based on IDisposable.

re: IRepository interface.

Anonymous — Thu, 19 Nov 2009 01:53:11 GMT

UnitOfWork. It's in PoEAA.

re: Shader effects kill performance of Silverlight popup control.

Rishi — Wed, 18 Nov 2009 12:31:27 GMT

Add to that anything draggable, it too suffers from having any shader applied on it.

Twitter Trackbacks for IRepository interface. - Alexey Zakharov's Blog [asp.net] on Topsy.com

Wed, 18 Nov 2009 06:00:12 GMT

Pingback from Twitter Trackbacks for IRepository interface. - Alexey Zakharov's Blog [asp.net] on Topsy.com

Twitter Trackbacks for Shader effects kill performance of Silverlight popup control. - Alexey Zakharov's Blog [asp.net] on Topsy.com

Wed, 18 Nov 2009 04:06:00 GMT

Pingback from Twitter Trackbacks for Shader effects kill performance of Silverlight popup control. - Alexey Zakharov's Blog [asp.net] on Topsy.com

Entity Framework - part 2

שלמה גולדברג — Sun, 25 Oct 2009 16:05:28 GMT

נמשיך בלימוד על Entity Framework. בפרק הזה נייצר את הישות הראשונה שלנו כמובן שנעשה זאת ידני - לאחר שנבין

re: Issues of Silverlight style system

Pete the Geek — Tue, 20 Oct 2009 09:26:35 GMT

The best way of loading themes involves dynamic loading of styles from the server and parsing them into the App Resources. You are correct in that the order of loading must reflect the dependancies of one style on another and must occur before you load the root element of your application.

Silverlight Cream for October 19, 2009 -- #711

Community Blogs — Tue, 20 Oct 2009 04:40:08 GMT

In this Issue: Davide Zordan , SmartyP , Corey Schuman , Gavin Wignall ( 2 ), Jeff Paries , Vikram Pendse

re: Issues of Silverlight style system

Alexey — Mon, 19 Oct 2009 09:42:26 GMT

Heh.. Silverlight is A BIG HACK =)

re: Issues of Silverlight style system

Rishi — Mon, 19 Oct 2009 06:32:50 GMT

Understood, thanks. I'll try this and a relaying approach, though all this will remain hack'ish till it is rightfully addressed at the framework level. Hopefully, in SL4.