| |
Genome Visual Studio 2017 Integration Update v1.0 release - Friday, April 07, 2017
Starting with Visual Studio 2017 the Genome Visual Studio integration is distributed as separate Visual Studio Extension. The extension can be downloaded from the professional and express download sections. The v1.0 version includes support for Data Domain Schema projects (mapping project, mapping files). Support for Genome Messaging Extension (WOPii) will be included in the next version.
|
Genome v4.2 SP10 released - Wednesday, May 18, 2016
Genome v4.2.11 provides fixes for the integration to Microsoft Visual Studio 2015. With the update DataDomain schema projects can be compiled to .NET 4.6.1 and .NET 4.6.2 as well. The service pack contains a few minor fixes in the Sqlite provider and in the runtime too.
|
Genome v4.2 SP9 released - Tuesday, September 22, 2015
Genome v4.2.10 provides integration to Microsoft Visual Studio 2015 with the same functionality as for VS2013. Also with this update the DataDomain schema projects can be compiled to .NET 4.5.2 and .NET 4.6 too. The service pack adds support for PostgreSql database and contains a few minor fixes in the runtime too.
|
Genome 4.2 SP8 supports VS2013 and .NET 4.5 - Thursday, October 24, 2013
Genome v4.2.9 provides integration to Microsoft Visual Studio 2013 with the same functionality as for VS2010 and VS2012. Also with this update the DataDomain schema projects can be compiled to .NET 4.5 and .NET 4.5.1 too. The service pack contains a few minor fixes in the runtime too.
|
Genome 4.2 SP7 released - Wednesday, May 01, 2013
With a few fixes and a small feature!
|
Genome 4.2 SP6 supports VS2012 RTM - Friday, August 24, 2012
Genome v4.2.7 provides integration to Microsoft Visual Studio 2012 RTM with the same functionality as for VS2010. This release contains only this tool enhancement and no change in the runtime.
|
Genome 4.2 SP5 with VS2012 RC support - Friday, June 29, 2012
Genome v4.2.6 provides integration to Microsoft Visual Studio 2012 RC with the same functionality as for VS2010. This release contains only this tool enhancement and no change in the runtime.
Important note: Visual Studio 2012 RC comes with a change in the MsBuild system, that causes the Genome builds fail (in VS2012 and also in VS2010) with the following error:
error MSB4185: The function "CurrentUICulture" on type "System.Globalization.CultureInfo" has not been enabled for execution.
This problem will be fixed my Microsoft in VS2012 RTM. In the meanwhile you have to set the environment variable “MSBUILDENABLEALLPROPERTYFUNCTIONS” to “1”. (You might need to restart Visual Studio).
|
Genome 4.2 SP2 (v4.2.3) released - Oct 29, 2010
With many fixes and small features!
read more...
|
Genome 4.2 released - Feb 10, 2010
Supports now Visual Studio 2010!
read more...
|
Updated roadmap - Dec 22, 2009
learn more about the upcoming Genome v4.2 release
read more...
|
Genome 4.1 released - Mar 31, 2009
Read more about what's new in this release.
read more...
|
New Product Video released - Jan 16, 2009
Get a quick overview of Genome v4.
read more...
|
|
|
| |
|
|
| |
|
|
|
| |
The Missing LINQ 
Object relational mapping with LINQ for .NET enterprise application development Genome O/RM uses LINQ to generate data access layers connecting relational database systems such as Microsoft SQL Server, Oracle and IBM DB2 to your .NET enterprise applications.
Since 20-80% of a .NET enterprise application's code deals with data access, Genome significantly reduces efforts for both development and maintenance.
Less code = less work Code generated by Genome is lean and clean: you not only save time when building, but can also make your code more agile and easier to maintain. Some quick facts about Genome: - Supports the .NET Framework (versions 2.0 to 4.5.1)
- Fully embraces LINQ as its primary query language (Visual Studio 2008/.NET 3.5 or later)
- Tightly integrates with Visual Studio 2005, 2008, 2010, 2012 and 2013
- Supports various database platforms (MS-SQL, Oracle, IBM DB2, SQLite)
- Supports both approaches: forward engineering from domain models, reverse engineering from databases
Sounds good so far, but you still have questions?
|
|
| |
|
|
| |
|
|
|