Re: Emulator skin issue - custom platform

As a follow-up to my earlier response, your workaround succeeds if I set the
Skin value to a valid full pathname to the xml file. However, if I clear
that property (or delete it altogether), VS.NET complains that the SDK is
corrupted due to a duplicate value and recommends that I reinstall the SDK.

Nandakumar


"Charles Gifford [MSFT]" <chasg@online.microsoft.com> wrote in message
news:icxFVRPQDHA.2416@cpmsftngxa09.phx.gbl...
> Nandakumar,
>
> This is a known issue with VS .NET and how it consumes emulator SDKs
> created with the Platform Builder SDK roller. The Configure SDK property
> pages within PB only allows the user to specify the folder where the Skin
> files reside, and then it doesn't specify a filename for the Skin value.
> VS .NET will then try to read in all of the registry key values created
for
> the managed platform and generate a sdkRollerDevice-[GUID].xsl file in the
> %allusersprofile%\Application Data\Microsoft\visualstudio\devices\addons
> directory, but it will not be specifying the XML filename for the Skin
> value. VS .NET then will fail to start the emulator.
>
> You can manually modify the sdkRollerDevice-[GUID].xsl file in the
> .\addons directory so that the Skin property value contains the
> appropriate XML filename for the Skin, and then restarting VS .NET
> afterwards should allow VS .NET to successfully launch the emulator with
> the BIN image and skin specified. Or you can remove the Skin property
value
> so that it is empty.
>
> Microsoft may release a tool in the future that will modify the MSI file
> created by the SDK roller and remove the Skin property so that the BIN
> image can be launched successfully within the emulator without errors. But
> it probably will not allow you to specify an XML filename for the Skin
> property.
>
> Charlie Gifford
> Test Engineer, Visual Studio for Devices
> Microsoft
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>