Lærte noget nyt om arv i dag…

Da jeg sad og skulle implementere et design, kom der en ide op omkring en variabel der skulle udbydes af en abstrakt klasse, for derefter at blive assignet i den nedarvende klasse.
Under selve implementeringen finder jeg på at gøre variablen readonly, men finder ud a at det ikke kan lade sig gøre.
Jeg troede, at så længe jeg assignede variablen i en konstruktør, var der ingen is på koen. Men der skulle jeg så lære noget nyt 🙂

Eksemplificeret ved følgende blok:

















Men visual studio skulle vise sig at kende til en begrænsning jeg ikke kendte (det er ikke første gang). Se screensnip:

Og tilhørende build fejl:

Slotskage i lyserød

Der begynder så småt at blive stillet større og større krav til udformning af kager til bestemte begivenheder i den lille familie.
Senest fylder den ældste 4 år på onsdag, hvorfor der den seneste tid er blevet eksperimenteret med tiltag i den retning.
Herunder ses forsøget på et prinsesseslot i skøn forening af smør, sukker, sukker, mel, smør, æg, mel, sukker, smør, æg og appelsin også bedre kendt som mazarinkage med glasur og vafler.

Den endelige kage, med hele baduljen kørt på 🙂

Setting the maximum allowed memory consumption by Analysis Services

Here follows the step to find where to change the settings for LowMemoryLimit, TotalMemoryLimit and other memory related properties of the SQL Server Analysis Services instance.

Fire up your SQL Server Management Studio, and right-click the server and select ‘properties’

Then check the ‘Show Advanced (All) Properties’ and you’ll see al available properties, like this example:

If values listed are between 0 and 100, they are treated as a percentage of the physical memory on the server. Otherwise they are treated as bytes.

A rather unfortunate bug… But aren’t they all?

The other day I was testing various charting components, including XCeed, Nevron and DevExpress. All components really looked nice in regards to API, Layout and Look N Feel.
I have run several tests on all three components, and have a hard time deciding which one to choose for our project (if any of the three).

Today I hit a strange behaviour with the DevExpress trial installation. While I was adding a class in VS2010, by right clicking and choosing ‘add class’ I got a lot more than just a class.
In fact the DevExpress trial package deemed it necessary to add a reference to every DevExpress library in the current project, see image:

DevExpress Issue 1

The fact that the project is a businesslayer makes matters worse…
I think DevExpress has some fixing to do 🙂

UPDATE:
This seems to have been caused by what I call a “Monday Computer”.
I havent been able to reproduce the bug, except for the day it occurred.
DevExpress has been very willing to help and very alert, through especially Mehul Harry and Seth Juarez