Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

Claim based security made easy

When we implemented claim based authorization in LitwareHR, we had to write a lot of code and play with non-trivial configurations (LitwarehR includes 2 STS and all the supporting infrastructure for securing the web services and the callers to them).

Simple GeoRSS utility library - released

I just uploaded the source code for this library, used in the Virtual Earth mash-up described in my previous post . You can browse/download it from here . What you will find: A simple domain model for GeoRSS feeds with support for points , lines and polygons
Posted by eugeniop | 6 Comments
Filed under: ,

LitwareHR and GeoRSS

Some time ago , I did some experiments with Virtual Earth control and its features. I especially liked the GeoRSS integration because it allowed very simple, straightforward, non-astronauts like me to do some very nice mashups. WCF support for creating

Another SSDS sample: BlogEngine.NET on SSDS

As a by-product of a project I'm working on, I've got a working version of BlogEngine.NET on SSDS. You can download the provider and other related components from LitwareHR's web site releases section here . In the package you will find: The SSDS based

You don't have a beta account with SSDS, but you'd like to use the latest LitwareHR anyway

Well, too bad...No, seriously now, as I mentioned in a previous post , we developed a "mock" (but fully functional for LitwareHR's purposes) offline SSDS proxy to enable development independently from the live SSDS service. The offline proxy

LitwareHR on SSDS available for download

The latest version of LitwareHR is now available for download here . From our CodePlex site: This new enhanced version of LitwareHR includes the following new features: Upgraded codebase for SQL Server Data Services support New "DataModel" New

Paging in SSDS & Parallel Queries

Tim Jarvis raised a good point in my post on cross-container queries which is: how to handle paging? SSDS currently supports a very simple paging pattern that uses the entityId . By design, the first 500 entities will be returned, but the entities will

End to end demo of LitwareHR on SSDS

Here's an end-to-end demo of LitwareHR using SSDS. The total demo lasts about 11 min and you will see: Tenant Provisioning and customization (takes the first 5 min approximately). I show the initial tenant provisioning (creation of a new tenant in LitwareHR,

LitwareHR on SSDS - Part VI - Unit of Work support

For years now, we have been using transactions in our systems. Years ago, there's been a democratization of the more complex concepts underlying transaction management and we've been quite happy. On the Microsoft side there's been technologies like: MTS,

More on parallel queries across containers in SSDS

Our current implementation of cross-Container queries follows a very common pattern and roughly looks like this (no exception handling shown for simplicity): public List<T> CrossContainerSearch( string [] containerIds, string query, SearchDelegate

LitwareHR on SSDS - Part V - Searching across Containers

In SQL Server Data Services, the scope of a query is bound to a Container , but in LitwareHR we had a requirement of searching entities across multiple tenants, and because in our implementation each tenant gets its own Container, we had to create a way

LitwareHR on SSDS - Part IV - Data access enhancements 2: developing offline

SQL Server Data Service is well...an online service. That means that you have to be connected to the network 100% of the time if you are using it. What if you are not connected? well...you know the whole story. Our goal while developing LitwareHR was

LitwareHR on SSDS - Part III - Data access enhancements 1: caching

In most applications, the distance (in terms of bandwidth and latency) between the store (the database) and the application logic (like the web servers and web services) is usually very small. The connectivity between these two components is usually very

LitwareHR on SSDS - Part II - The data access layer

The heart of LitwareHR implementation on SSDS is in it's data access layer of course. In fact, we created two different, but functionally equivalent implementations: one runs against SQL (LitwareHR's original implementation) and a second stack that runs

LitwareHR on SSDS - Part I - Multi-tenancy & Flexibility

SSDS's application model and features map quite nicely to our customization and multi-tenancy requirements in LitwareHR. A significant amount of code in LitwareHR is in the generic, multi-tenant, extensible data access. Our multi-tenant database performance
More Posts Next page »
 
Page view tracker