This question is locked. New answers and comments are not allowed.
Eddie Conner
Top achievements
Rank 1
Rank 1
Eddie Conner
asked on 18 Jul 2010, 12:11 AM
I am a user of VistaDB and I have the source code edition and I am looking at making some custom changes. According to their documentation they suggest changing the assembly names and versions to prevent conflict with the standard product.
Is it possible with the OpenAccess ORM source code to add my custom VistaDB assemblies. This basically is a copy of the OpenAccess ORM VistaDB classes. Are all of the source files included in the OpenAccess ORM source edition to recompile OpenAccess?
Is it possible with the OpenAccess ORM source code to add my custom VistaDB assemblies. This basically is a copy of the OpenAccess ORM VistaDB classes. Are all of the source files included in the OpenAccess ORM source edition to recompile OpenAccess?
5 Answers, 1 is accepted
0
Hi Eddie Conner,
It is not a good idea to compile the OpenAccess code by yourself, the source code is more ment for debugging purpose. If you use a different version number for your self compiled VistaDB and use assembly redirection it should work without a problem and you do not have conflicts between your self build and the original VistaDB version.
All the best,
Jan Blessenohl
the Telerik team
It is not a good idea to compile the OpenAccess code by yourself, the source code is more ment for debugging purpose. If you use a different version number for your self compiled VistaDB and use assembly redirection it should work without a problem and you do not have conflicts between your self build and the original VistaDB version.
All the best,
Jan Blessenohl
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
0
Eddie Conner
Top achievements
Rank 1
Rank 1
answered on 19 Jul 2010, 04:46 PM
Thanks for the suggestion on versioning.
Also, I understand the source is mostly for debugging, but say something extreme happened and say OpenAccess was discontinued. Would the source code of OpenAccess be abled to be compiled if a bug was found or a feature was needed? Basically, is everything included with the source to be able to continue if needed?
Again, I know this is an extreme example, but it is something I have to consider in the development of a project I am working on.
Also, I understand the source is mostly for debugging, but say something extreme happened and say OpenAccess was discontinued. Would the source code of OpenAccess be abled to be compiled if a bug was found or a feature was needed? Basically, is everything included with the source to be able to continue if needed?
Again, I know this is an extreme example, but it is something I have to consider in the development of a project I am working on.
0
Hello Eddie Conner,
In the text file that accompanies the source code, you will find that not all of the code base is provided, due to various reasons. What is provided is the complete runtime code. The tooling (Enhancer, Schema tool) and design-time integration (Visual Designer, AddIn, etc.) are not provided in the source code distribution.
Kind regards,
Dimitar Kapitanov
the Telerik team
In the text file that accompanies the source code, you will find that not all of the code base is provided, due to various reasons. What is provided is the complete runtime code. The tooling (Enhancer, Schema tool) and design-time integration (Visual Designer, AddIn, etc.) are not provided in the source code distribution.
Kind regards,
Dimitar Kapitanov
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
jeff357
Top achievements
Rank 2
Rank 2
answered on 06 Jan 2011, 12:21 AM
Hello all.
Telerik people>>> VistaDB 4.0 and earlier are NO MORE
no longer available or supported by the new vistadb team...
4.1 is a unprotected build that includes full source code
4.2 will be available early spring (very early). Telerik
folks please do as you do with ms-sql just allow any
version 4 vistadb to work with Telerik OEM Please...
I desparately need orm... pdq asap now sooner than later
all versions 4.0 and below are protected and the activation
server is no more.
Greetings,
Dr. Jeff Link
Telerik people>>> VistaDB 4.0 and earlier are NO MORE
no longer available or supported by the new vistadb team...
4.1 is a unprotected build that includes full source code
4.2 will be available early spring (very early). Telerik
folks please do as you do with ms-sql just allow any
version 4 vistadb to work with Telerik OEM Please...
I desparately need orm... pdq asap now sooner than later
all versions 4.0 and below are protected and the activation
server is no more.
Greetings,
Dr. Jeff Link
0
Kendall
Top achievements
Rank 1
Rank 1
answered on 06 Jan 2011, 12:56 AM
Dr. Link -
We're working with each customer that's still running VistaDB 3.x to provide good options to get up to 4.1 and the 4.2 version when we ship that. It's unfortunate that we can't process 4.0 activations any more, but please contact us to see if there's something we can do to help you out in the short term. If you are licensed for VistaDB 3 while we aren't providing any defect fixes to that codebase the engine itself doesn't require local activation to work.
We're working with each customer that's still running VistaDB 3.x to provide good options to get up to 4.1 and the 4.2 version when we ship that. It's unfortunate that we can't process 4.0 activations any more, but please contact us to see if there's something we can do to help you out in the short term. If you are licensed for VistaDB 3 while we aren't providing any defect fixes to that codebase the engine itself doesn't require local activation to work.