|
-
Jan 7th, 2009, 04:21 PM
#1
[RESOLVED] [2008] Delopying interop.wuapilib.dll
Hi Guys,
I've made a little console app that uses the Windows Update APIs to download and install some specific updates (namely Exchange 2003 IMF updates) with the idea being that this would be run automatically every week or whatever to download new updates for the Exchange IMF.
Anyway, I added a reference to the file C:\Windows\System32\wuapi.dll and that gave me access to all of the necessary classes etc to use in VB.NET to work with the Windows Update commands. I (foolishly) assumed that any system that also had this wuapi.dll file installed would be able to run my app but it seems that when I build my application it generates a file named interop.wuapilib.dll in my Release directory. If I dont copy this file to the same location that my app is being run from then my app just crashes on launch.
So, after all that, my question is: Am i legally allowed to distribute this DLL file with my application? I did a bit of google searching but couldn't find anyone else asking the same question or any reference to distributing this DLL so how do I know?
Thanks
Chris
-
Jan 7th, 2009, 06:16 PM
#2
Re: [2008] Delopying interop.wuapilib.dll
Yes, that's an interop class library that lets your .NET app talk to a COM class library (wuapi.dll). I'd assume that wuapi.dll is available on the target machines, unless windows update has changed drastically across OS versions, so you probably won't need to distribute that. But the Interop is yours, so feel free to do with it as you please.
-
Jan 7th, 2009, 06:25 PM
#3
Re: [2008] Delopying interop.wuapilib.dll
Ah cool thanks yeah wuapi.dll is available in that location that I mentioned on XP, Vista and Server 2003 so I should be fine just sticking the interop assembly in with my app install.
Thanks
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|