EntitySpaces
Persistence Layer and Business Objects for Microsoft .NET
Purchase ES2008 and get started today.
 |
You will also receive 1 year of free upgrades which will include our ES2009 release which is already in the oven and runs within Visual Studio. See Part 1 and Part 2 on our blog. Also, Subscribe to our BLOG and keep up with what's going on with EntitySpaces. Take a look at our ES2009 Roadmap. |
Get Started Today:
- Requires the Microsoft .NET Framework 2.0 or higher
- Install MyGeneration 1.2 which you can find HERE or CodeSmith which you can find HERE.
- Next install the EntitySpaces 2008 Trial, which you can find HERE
- Watch our Presentation (takes a few minutes to load) for MyGeneration or CodeSmith
Example Source

Features:
Providers Available:
- Microsoft SQL Server / SQL CE
- Microsoft Access
- Oracle
- MySQL
- VistaDB
- PostgreSQL
|
EntitySpaces on .NET Rocks Mike Griffin, of EntitySpaces, talks with Carl and Richard about EntitySpaces, a persistence layer and business object system for the Microsoft .NET 2.0 Framework, as well as his experiences with LINQ and other technologies.
|
From mobile devices to large scale enterprise solutions in need of serious transaction support, EntitySpaces is the development tool that can meet your needs. Whether you’re writing an ASP.NET application with medium trust requirements, or a Windows.Forms application, the EntitySpaces architecture is there for you. EntitySpaces is provider independent, which means that you can run the same binary code against any of the supported databases. EntitySpaces is available in both C# and VB.NET. EntitySpaces uses no reflection, no xml files, and sports a tiny foot print of less than 200k. Pound for pound, EntitySpaces is one tough .NET architecture.
Although EntitySpaces targets both ASP.NET and Windows.Forms projects, DotNetNuke module developers will find EntitySpaces to be an attractive alternative to the DotNetNuke DAL. Many of the features listed above, including important ones like transactions, are not available when using the DotNetNuke DAL API. The EntitySpaces provider independence model we feel is much easier because it is basically transparent and provided by EntitySpaces itself. It is not left up to you, the developer, to create. EntitySpaces handles it for you. There is a sample DotNetNuke module on our main menu, take a look at the source code listing too.