If someone has a suggestion of how to handle .NET dll assembly versions in a SQL Server 2008 database I would be very happy if you could explain how to do it.
First some background though so you'll understand the situation I'm in.
I've created a SQLCLR stored procedure in .NET with some code doning calculations in the database. Now I need to update the code according to some new business rules. Unfortunately we don't have a test environment where I can upload the code and test it
until it works. Therefore I would like make the changes necessary in the code and somehow change the version number of the dll and deploy that to the database while the old dll is still used in production.
I've heard of the workaround with strong/weak assembly names but I'm wondering if there's a real versioning method around yet.
And yes I know the "easiest" way would be to create a testenvironment and ahve the normal setup with test/production servers but I still would like to know if my original idea is possible in any way.
View Complete Post