Archives
-
Strongly Typed Delete With NHibernate
To my great satisfaction, LINQ is nowadays present everywhere, from XML processing, to database querying, including SharePoint. The “Q” in it standing for Query, it’s not a surprise that is mainly being used for querying, but it would be interesting to use it for other scenarios, such as updating and deleting.
-
NHibernate Pitfalls: Querying Unmapped Properties With LINQ
This is part of a series of posts about NHibernate Pitfalls. See the entire collection here.
-
Using the ASP.NET Health Monitoring Provider to Secure Your Application in the Case of an Attack
The ASP.NET Health Monitoring is a featured introduced in ASP.NET 2.0. Basically, you have your application raise web events – not to be confused with user interface events – and you configure rules that define, for a given event code or range of event codes, a time interval and a minimum and maximum number of occurrences, the health monitoring provider that the events will be routed to. The ASP.NET infrastructure already raises a number of these events, and you can also define your own events, and take the responsibility to raise them when appropriate. I won’t go into describing how the health monitoring works, there are several web sites that describe it, instead, I will talk about a different use.
-
NHibernate Pitfalls: Eager Loading Multiple Collections
Updated on July 19. Thanks, Hazzik!
-
Using ASP.NET Resources in JavaScript
If you use resources in your web application to localize your strings on the server side, you may have also felt the need to use the same resources in JavaScript. The thing is, there wasn’t any straightforward way to do it. Until now, that is!
-
NHibernate Pitfalls: Cascades
This is part of a series of posts about NHibernate Pitfalls. See the entire collection here.
-
NHibernate Pitfalls: Lazy Scalar Properties Must Be Auto
This is part of a series of posts about NHibernate Pitfalls. See the entire collection here.
-
Vote of Disconfidence to Entity Framework
A friend of mine has found the following problem with Entity Framework 4: