We have an app running in CLR that schedules our homeless shelter. We need to setup the calendar TODAY and never thought it would have just "stopped working," but apparently with this new "v3," none of the methods we've used for Years will work with our app.
We have these .dlls imported into MSSQL so we can use them inside of a CLR stored procedure (.vb):
I assume we now need these .dlls:
I need to: Get the .dll's to work with MSSQL 2008R2 which I assume means they need to work with .NET 2.0.
Does anyone have any experience here? Please help. Thanks.
Hi there. Can you please be a little more specific? "v3" of what? Google something-something? Do you mean that your app, running inside of SQL Server's CLR (i.e. SQLCLR) is / was communicating with Google Calendar? If so, then sounds interesting.
In general, if you are saying that Google updated their API (or maybe more accurately sunset a prior API--which they do often enough whether anyone likes it or not, for they are the Google), then yes, you have to conform to their new API.
Regarding the version of .Net: SQL Server 2008 R2 is statically linked to the 2.0 series of the .Net framework, but should be able to use functionality going up through .Net 3.5. HOWEVER, that requires that .Net 3.5 (and likely also .Net 3.0) are installed on the server running SQL Server. And it requires that you might need to load additional framework assemblies that might be referenced by the Google DLLs, and that is not guaranteed to work, even if loaded as UNSAFE. For example, SQL Server only allows pure .Net DLLs (i.e. only MSIL) and not mixed. So, if a Google DLL references a 3.0 framework library that is not already part of the internal CLR, and if that framework library is mixed (even if it was "pure" in .Net 2.0), then I don't think there is any way to load it. But you won't know until you load all of the Google DLLs and then try to call the methods in them that reference .Net framework methods.
Does this help at all? I hope at least a little.