Re: Carbide.vs 3.0.1 for VS2005 tips and issues

[VirGin]

Hi,

This problem is still present.

I downloaded Carbide VS in mid-June. I attempted to install it after installing the SDK which I also downloaded in mid-june.

The path mentioned in the workaround does not exist after I installed the SDK. As a side note, my program files directory is not on the C: drive. Typical Symbian lack-of-thought.
Regardless, the directory SDK Descriptors branch is in /Common Files/ not /Common Files/Symbian after install.

I modified the registry to skip the check. It doesn't have any effect.


Symbian needs to start taking this whole 'development' thing seriously.


-V-

[ltomuta]

Let's not add more to the sticky thread, unless we discuss the issue and find that we should add something there that is relevant to all the readers.

On my computer the path is correct and I do not see why would it be different in your case. I also don't have (never had) problems installing a Symbian SDK so let's start it over and I'm sure will get it work.

If you have the SDK installed there is no point in modifying the registry key. The only relevant thing is to add the file to the specified path, of course on your system drive (if not C: - that is a good point, I will update the page).

[VirGin]

Hola,

Fair enough.
However, I will say that these types of issues are a trend with Symbian.

Paths:
%SystemRoot% (%WinDir%) == D:\Abydos\.

%ProgramFiles% == 'D:\Program Files\'.
Note: I have, in the past changed this to drive other than the drive %systemroot% is on.

SDK Install == D:\SDK\Symbian\S603rdFP2\.

SDK Installer created S60_3rd_FP2_SDK, which is not what I wanted.

SDK Descriptor Directory == 'D:\Program Files\Common Files\SDK Descriptors'.
According to the Carbide VS Dox (which don't match what I see in other areas also), the path should have been == 'D:\Program Files\Common Files\Symbian\SDK Descriptors'.

Missing SDK Descriptor Directory.
The documentation stated that there should be '/Symbian/SDK Descriptors/Nokia/' in Common Files. This path did not exist.


Procedure:
The machine had CarbideUI installed on it about two weeks ago (mid-june).
An attempt was made to install CarbideVS. The installer could not see the SDK.
Installed SDK.
Attempted to install CarbideVS. The installer still did not see the SDK.
Attempted to use workaround (downloaded XML file). Created directory as specified in workaround message.
Attempted to install CarbideVS. The installer still did not see the SDK.
Modified registry per workaround message.
Attempted to install CarbideVS. The installer still did not see the SDK.

At this point I posted the previous message.

I rebooted the machine and tried the VS install again. It did not see the SDK, but the download button was disabled and the 'next' button was enabled. I was able to continue.



Was this one better?



-V-