Return to Answer

##soapi.js vs soapi-vsdoc.js

While the -vsdoc.js is quite large, it is never served. It is, if you are using Visual Studio, used to provide intellisense services, otherwise you may either delete it or keep it around as reference.

The file that actually defines the domain types at runtime, soapi.js, is quite small, 9.5k packed, in that it only contains meta data that is used at 'compile' or more accurately parsing time to dynamically build the domain objects.

There is a slight performance hit to be taken when using new Function() when compared to inline code but I have not seen that to be an issue, especially when you are dealing with network requests. It is my observation that an app using Soapi.js will be network bound as opposed to CPU bound.

soapi.js vs soapi-vsdoc.js

While the -vsdoc.js is quite large, it is never served. It is, if you are using Visual Studio, used to provide intellisense services, otherwise you may either delete it or keep it around as reference.

The file that actually defines the domain types at runtime, soapi.js, is quite small, 9.5k packed, in that it only contains meta data that is used at 'compile' or more accurately parsing time to dynamically build the domain objects.

There is a slight performance hit to be taken when using new Function() when compared to inline code but I have not seen that to be an issue, especially when you are dealing with network requests. It is my observation that an app using Soapi.js will be network bound as opposed to CPU bound.

##Implementation Note #1

While the -vsdoc.js is quite large, it is never served. It is, if you are using Visual Studio, used to provide intellisense services.

The file that actually defines the domain types at runtime, soapi.generated.js, is quite small in that it only contains meta data that is used at 'compile' or more accurately parsing time to dynamically build the domain objects.

There is a slight performance hit to be taken when using new Function() when compared to inline code but I have not seen that to be an issue, especially when you are dealing with network requests. It is my observation that an app using Soapi.js will be network bound as opposed to CPU bound.

##soapi.js vs soapi-vsdoc.js

While the -vsdoc.js is quite large, it is never served. It is, if you are using Visual Studio, used to provide intellisense services, otherwise you may either delete it or keep it around as reference.

The file that actually defines the domain types at runtime, soapi.js, is quite small, 9.5k packed, in that it only contains meta data that is used at 'compile' or more accurately parsing time to dynamically build the domain objects.

There is a slight performance hit to be taken when using new Function() when compared to inline code but I have not seen that to be an issue, especially when you are dealing with network requests. It is my observation that an app using Soapi.js will be network bound as opposed to CPU bound.

##Implementation Note #1

While the -vsdoc.js is quite large, it is never served. It is, if you are using Visual Studio, used to provide intellisense services.

The file that actually defines the domain types at runtime, soapi.generated.js, is quite small in that it only contains meta data that is used at 'compile' or more accurately parsing time to dynamically build the domain objects.

There is a slight performance hit to be taken when using new Function() when compared to inline code but I have not seen that to be an issue, especially when you are dealing with network requests. It is my observation that an app using Soapi.js will be network bound as opposed to CPU bound.

##Implementation Note #1

While the -vsdoc.js is quite large, it is never served. It is, if you are using Visual Studio, used to provide intellisense services.

The file that actually defines the domain types at runtime, soapi.generated.js, is quite small in that it only contains meta data that is used at 'compile' or more accurately parsing time to dynamically build the domain objects.

There is a slight performance hit to be taken when using new Function() when compared to inline code but I have not seen that to be an issue, especially when you are dealing with network requests. It is my observation that an app using Soapi.js will be network bound as opposed to CPU bound.