When one deploys a CLR DLL that contains [SqlFunction]'s, Visual Studio creates three extended properties on the SQL function that is created: these are,
AutoDeployed, SqlAssemblyFile, SqlAssemblyFileLine.
What I haven't found anywhere on Help or MSDN online is what these extended properties mean.
Could someone enlighten me?
1. What is a description of the above properties?
2. What is the benefit of using them (clearly the function works without using them). Does it help debugging?
3. Does the developer need to manually keep for instance the SqlAssemblyFileLine in sync with changes in the .NET code?
Thanks a lot.
Aneela_B wrote:
When one deploys a CLR DLL that contains [SqlFunction]'s, Visual Studio creates three extended properties on the SQL function that is created: these are,
AutoDeployed, SqlAssemblyFile, SqlAssemblyFileLine.
What I haven't found anywhere on Help or MSDN online is what these extended properties mean.
Could someone enlighten me?
1. What is a description of the above properties?
2. What is the benefit of using them (clearly the function works without using them). Does it help debugging?
3. Does the developer need to manually keep for instance the SqlAssemblyFileLine in sync with changes in the .NET code?
AFAIK, the above properties do not have any use at the moment. They have no impact on debugging.
If you change the .NET code you have to re-deploy your assembly (either CREATE or ALTER).
Niels
No comments:
Post a Comment