In article <be4aks$13c18$1@ID-151790.news.dfncis.de>, Frank Matthiesen
<fm@xax.de> writes
[quoted text, click to view] >
>"Darren Green" >
>> Not with me now, I'll try and dig something out later.
>>
>> > Wich entries are needed?
>> Pretty much as per the books online topic.
>>
>> Do i need to refresh the cache after registering
>> > the new task?
>
>Doesn't matter. I will setup regmon,register some custom task and will see.
>Should be possible to get the needed entries.
>
>best regards from bextown/germany
>
>do you interest in beer, do you?
>
Of course!
I used Visual Studio Installer (VSI) to create my MSI packages, from a
VB project. I set the compiled DLL to self-register, and also add the
following registry keys manually to the VSI solution-
HKEY_CLASSES_ROOT
-----------------
Key: CLSID\{Class ID for Component.CTaskClass}
Name: (default)
Value: Component.CTaskClass
Type: String
Name: AppID
Value: {Class ID for Component.CTaskClass}
Type: String
Name: DTSIconFile
Value: \path\iconfile.ext|\path\customtask.dll
Type: String
Name: DTSIconIndex
Value: 0
Type: DWORD
Name: DTSTasKDescription
Value: Default Task Description
Type: String
Key: CLSID\{Class ID for Component.CTaskClass}\Implemented
Categories\{Class ID for DTS Library}
HKEY_CURRENT_USER
-----------------
(SQL Server 2000 Only)
Key: SOFTWARE\Microsoft\Microsoft SQL
Server\80\DTS\Enumeration\Tasks\{Class ID for Component.CTaskClass}
HKEY_LOCAL_MACHINE
------------------
Same keys and values as HKEY_CLASSES_ROOT above
I'm not that good on COM, but if you register the custom task manually,
and then use the "OLE View" tool that comes with Visual Studo 6..0 you
will see a nice section for custom tasks. Compare yours with the others
for interest, and it will also give your the CLSID.
--
Darren Green (SQL Server MVP)
DTS -
http://www.sqldts.com