This question is locked. New answers and comments are not allowed.
Kendall Bennett
Top achievements
Rank 2
Rank 2
Kendall Bennett
asked on 19 Jul 2011, 04:11 PM
Is there any reason why the source code for OpenAccess is not provided in a form that allows it to be compiled so we can build, debug and run using a library built from the source code? One of the primary reasons that I purchased OpenAccess was due to the fact that the source code was available, as that is an important consideration for me. It was important to me that I have access to the source code so that we will have the ability to do bug fixes between official releases as necessary, but as it stands the source code that is provided is useless.
If you look on this page, it says the FULL SOURCE CODE is included:
http://www.telerik.com/purchase/individual/orm.aspx
The little popup says 'Full C# and JavaScript source code', which is not true at all!
Now I am stuck because I have run into issues with the Q2 release of Telerik, and since the source code is essentially useless, I am stuck. I was hoping I would be able to build from the source code so I can debug into the code to work out the issues that I am having to see if there is something I can do to fix it, but now I cannot.
Unless there is some really compelling reason why the runtime source code for OpenAccess is NOT compilable, I think it should be provided. It would appear that all the source code is there, but there are no project files to build it. So not making it buildable is not really going to protect it at all since the source is provided, and if a competitor wants to figure out what you are doing they already have what they need. I am sure someone could probably figure out how to build projects for it if they REALLY wanted to, but I paid for full source code and it should be provided with project files (like most other Telerik projects).
If you look on this page, it says the FULL SOURCE CODE is included:
http://www.telerik.com/purchase/individual/orm.aspx
The little popup says 'Full C# and JavaScript source code', which is not true at all!
Now I am stuck because I have run into issues with the Q2 release of Telerik, and since the source code is essentially useless, I am stuck. I was hoping I would be able to build from the source code so I can debug into the code to work out the issues that I am having to see if there is something I can do to fix it, but now I cannot.
Unless there is some really compelling reason why the runtime source code for OpenAccess is NOT compilable, I think it should be provided. It would appear that all the source code is there, but there are no project files to build it. So not making it buildable is not really going to protect it at all since the source is provided, and if a competitor wants to figure out what you are doing they already have what they need. I am sure someone could probably figure out how to build projects for it if they REALLY wanted to, but I paid for full source code and it should be provided with project files (like most other Telerik projects).
1 Answer, 1 is accepted
0
Hi Kendall Bennett,
You have correctly noticed that our web site describes the source code package as “full”. Unfortunately that is not a correct statement and will be changed for the next release.
In order to build the entire source code and use it as a normal distribution one would need a huge set of additional tools and software, which is not normally present on a developer's machine, as well as some complex build scripts. That is why we can assure you there would be no value in deploying the whole OpenAccess code.
What we do provide is the sources for the “runtime” behavior of the product and the PDB files needed. They are intended mostly for debugging and exploratory purposes. For detailed information regarding the source code package contents, please refer to the SourceCodeReadme.txt file within the package.
We have checked and confirmed that project files are omitted from the released source code. This is not intentional and will certainly be addressed in our next official release. Please accept our apologies for the situation and for the inconvenience it has caused.
Best wishes,
Ivailo_I
the Telerik team
You have correctly noticed that our web site describes the source code package as “full”. Unfortunately that is not a correct statement and will be changed for the next release.
In order to build the entire source code and use it as a normal distribution one would need a huge set of additional tools and software, which is not normally present on a developer's machine, as well as some complex build scripts. That is why we can assure you there would be no value in deploying the whole OpenAccess code.
What we do provide is the sources for the “runtime” behavior of the product and the PDB files needed. They are intended mostly for debugging and exploratory purposes. For detailed information regarding the source code package contents, please refer to the SourceCodeReadme.txt file within the package.
We have checked and confirmed that project files are omitted from the released source code. This is not intentional and will certainly be addressed in our next official release. Please accept our apologies for the situation and for the inconvenience it has caused.
Best wishes,
Ivailo_I
the Telerik team
Register for the Q2 2011 What's New Webinar Week. Mark your calendar for the week starting July 18th and book your seat for a walk through of all the exciting stuff we will ship with the new release!