.NET Framework 2.0 question

This question also posted to microsoft.public.sqlserver.notificationsvcs.

Notification Services on SQL 2005 utilizes .NET Framework version 2.0.
(correct?)

If so, will there be a version of
microsoft.sqlserver.notificati­onservices.dll for SQL 2005 NS that will
allow me to create subscription management applications using VS 2003
and .NET Framework 1.1? Or must I use VS 2005 and .NET Framework 2.0?

Thanks,
Peter

Hi Peter -

SQL Server 2005 does come with v2.0 of the .NET framework, but I cannot speak as to whether Notification Services uses it or a prior version.

I'm setting up a test vpc for the exact scenario you mentioned. I expect it to work.

Here is an excerpt from BOL (April CTP) that doesn't directly address your question, but still may be applicable.

<excerpt>
Notification Services could not create an instance of the event provider. This error can occur if a custom event provider was not built using version 1.0.3705 of the .NET Framework. When Notification Services and a custom component use different versions of the .NET Framework, differences in the class libraries can cause application errors.

UserAction
When possible, build custom components with version 1.0.3705 of the .NET Framework. If you must build custom components with version 1.1.4322 of the .NET Framework, you can force Notification Services to use the same version. To do this, add a <startup> node to the NSService.exe.config file, which is in the vN.N.N.N\Bin folder of Notification Services. The following example shows the <startup> node:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>
<supportedRuntime version="v1.0.3705"/>
</startup>
...

The <supportedRuntime> elements restrict the versions of the .NET Framework that Notification Services can use. The order of the listed versions determines the order in which Notification Services attempts to load the .NET Framework versions. In the example above, Notification Services will first attempt to load version 1.1.4322 of the .NET Framework. If it is not available, Notification Services will attempt to load version 1.0.3705 of the .NET Framework.
You must restart the instance of Notification Services to apply changes made to NSService.exe.config.

</excerpt>
Of course you can still use COM Interop, but who would want to do that? :)

HTH...

--
Joe Webb
SQL Server MVP

~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811

I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)

|||Peter,
Notification Services in SQL Server 2005 requires the .NET Framework 2.0. There is no version of the notification services dll built against version 1.1 in SQL Server 2005.

The only way I know of to work around this, if you must build your client app against the .NET framework 1.1, is to create a web service wrapper around the NS APIs you need, using the .NET Framework 2.0. You will then be able to invoke methods on the web service from a .NET 1.1 application.

Obviously, this method is a little cumbersome. If at all possible, I highly recommend you move your subscription management application to .NET 2.0.

-shyam

Learn more about SQL-NS:
http://www.amazon.com/exec/obidos/tg/detail/-/0672326647/

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.|||

So, are BOL docs in the April CTP wrong in this respect? (I haven't checked the June CTP yet.)

--
Joe Webb
SQL Server MVP

~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811

I support PASS, the Professional Association for SQL Server. (www.sqlpass.org)

|||

No, there is no version of the microsoft.sqlserver.notificati­onservices.dll that can be called from .Net Framework 1.1. You will need to use .Net Framework 2.0.

-Lukasz

|||It seems like that content was held over from the NS2.0 release - it doesn't apply to SQL 2005. I'll check with our doc writer to have it removed/corrected.
Thanks
-shyam|||

This topic had not been updated for SQL Server 2005. The topic was rewritten shortly after the April CTP. Sorry about the old content.

|||Thank you everyone for the quick responses!

Peter