 |
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
 |
|
|
|
|
|
|
|
|
|
|
© 2007 2Top Software Engineering GmbH. All rights reserved. Legal Information | Privacy Statement |
support |
||
|
|
|
|
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
|
|
|
|
|
|
|
|
|
|
© 2007 2Top Software Engineering GmbH. All rights reserved. Legal Information | Privacy Statement |
support |
||
|
|
|
|
| ||
A: Zero Configuration means that there is no need to provide any configuration information to | | |
Persistor.NET® to be able to save, retrieve or delete object graphs to and from a data store. | | |
Persistor.NET® is designed to become productive with as little effort as possible. Persistor.NET® is | | |
able to extract all required information from the object graphs it has to handle. Refer to the | | |
download section to see the 5 steps to become productive with Persistor.NET®. | | |
| ||
| ||
A: Even for object graphs of medium complexity it is not easy to list each and every single type which | | |
will be stored in the data store. Persistor.NET® creates tables when there are new types of objects | | |
to be saved. | | |
| ||
| ||
A: Persistor.NET® detected that your ‘type’ does not support .NET Serialization. Persistor.NET® does | | |
not implement a proprietary mechanism but is based on .NET Serialization. Just tag your ‘type’ | | |
with the [Serializable] attribute or implement the ISerializable interface to make your type serializable. | | |
Refer to Object Serialization in the .NET Framework (http://msdn.microsoft.com/library/default.asp? | | |
url=/library/en-us/dndotnet/html/objserializ.asp) for a complete and detailed documentation. | | |
| ||
| ||
A: The type system of the CLR provides rich Meta Data about each runtime object. Persistor.NET® | | |
extracts all information it needs from Meta Data of the types to be saved, retrieved or deleted. | | |
Persistor.NET® extracts the required information as it is needed. Therefore you do not have to provide | | |
any mapping information in advance. | | |
| ||
| ||
A:Persistor.NET® is designed to support full fledged object oriented models. Independent from how | | |
often one particular object is referenced within an object graph, Persistor.NET® guarantees that each | | |
object in the graph is touched once and only once when being saved, retrieved or deleted. | | |
| ||
| ||
A: When an object is saved for the first time a 128 bit GUID is created for that object. | | |
| ||
| ||
A: No! The object ID is transparent to your business classes. The object ID is handled by | | |
Persistor.NET® automatically and transparent to you. You do not have to care about the object ID in | | |
any way. | | |
| ||
| ||
A: No! Persistor.NET® creates and fills a database from a given object model. An existing database | | |
which was not created by Persistor.NET® cannot be used. | | |
| ||
| ||
A: Yes! Persistor.NET® does not require proprietary preconditions. When the classes from your 3rd | | |
party assembly implement .NET Serialization, they can be stored, retrieved and deleted with | | |
Persistor.NET®. | | |
| ||
| ||
A: Yes! Persistor.NET® also works with SQL Server 2005 instead of SQL Server 2005 Express. | | |
| ||
| ||
A: Yes! Persistor.NET® comes with assemblies which are CLS-compliant. You can use any .NET | | |
Programming Language (like VB.Net, managed C++,...) to use Persistor.NET®. | | |
| ||