smuppy
5th June 2009, 12:34 PM
I have a few keys I want to delete using xml-provisioning:
<characteristic type="Registry">
<nocharacteristic type="HKLM\Services\SqmUpload"/>
<nocharacteristic type="HKLM\Services\BTAGSVC"/>
<nocharacteristic type="HKLM\Services\BthAsPlugin"/>
</characteristic>
When I built the cab, I checked the _setup.xml and it looks fine, nothing odd there. When trying to install on a fresh device (hardware reset, htc 7500 running wm 6.1) i get "RegTest1 cannot be installed".
I came to the conclusion that these three values are not deleteable using post-xmlprovisioning, but I dont know why and if there is any way to circumvent this:
<nocharacteristic type="HKLM\Services\HTCSENSOR"/>
<nocharacteristic type="HKLM\Services\HTCSENSOR2"/>
<nocharacteristic type="HKLM\Services\Gsensor"/>
The above three values are not producing this error and they also get deleted from the registry correctly.
Does anyone know the cause for this behaviour and maybe even a solution? Can it be that I need to set a DWORD (Flags=4) first so that the services wont load on boot? But I should be able to delete the damn key anyway i think...
I am not a coder so if the solution is a codesnippet in a setup.dll or similar, I'll have to learn C# :)
<characteristic type="Registry">
<nocharacteristic type="HKLM\Services\SqmUpload"/>
<nocharacteristic type="HKLM\Services\BTAGSVC"/>
<nocharacteristic type="HKLM\Services\BthAsPlugin"/>
</characteristic>
When I built the cab, I checked the _setup.xml and it looks fine, nothing odd there. When trying to install on a fresh device (hardware reset, htc 7500 running wm 6.1) i get "RegTest1 cannot be installed".
I came to the conclusion that these three values are not deleteable using post-xmlprovisioning, but I dont know why and if there is any way to circumvent this:
<nocharacteristic type="HKLM\Services\HTCSENSOR"/>
<nocharacteristic type="HKLM\Services\HTCSENSOR2"/>
<nocharacteristic type="HKLM\Services\Gsensor"/>
The above three values are not producing this error and they also get deleted from the registry correctly.
Does anyone know the cause for this behaviour and maybe even a solution? Can it be that I need to set a DWORD (Flags=4) first so that the services wont load on boot? But I should be able to delete the damn key anyway i think...
I am not a coder so if the solution is a codesnippet in a setup.dll or similar, I'll have to learn C# :)