Note: There is a new version of Carbide.vs out: Carbide.vs 2.0.2. Get it at:
Here is a list of things to consider when moving from Carbide.vs 2.0 to 2.0.1:
- Before you install Carbide.vs 2.0.1, uninstall both Carbide.vs 2.0 and Carbide.vs 2.0 Help.
- If you want to work with the Nokia S60 3.0 SDK, download and install the Final version of the SDK. Carbide.vs 2.0.1 no longer supports the S60 3.0 Beta.
- 2.0.1 enables developers to turn on and off autogeneration of the UID.cpp file. For existing projects, the default for this is "do not generate", for new projects (created with 2.0.1), the default is "generate". If you have developed projects using 2.0 for the S60 3.0 Beta, the UID.cpp content is incorrect. To get a correct UID.cpp file, you can either enable automatic UID.cpp file generation in the "Carbide.vs properties" for each project or you can manually edit the UID.cpp file.
- The default UID3 generated by Carbide.vs 2.0 is in the Protected range. When moving to 2.0.1, if you want to test on a phone, you either need to get a Symbian Signed Developer certificate or change the UID value to a supported value in the unprotected range (range E). For details on how to get a SymbianSigned developer certificate, see the Carbide.vs Online Help (section How to's -> How To Create a Developer Certificate for Carbide.vs Using the DevCert Tool). For information on how to change the UID in Carbide.vs, see also Online Help (section How to's -> How To Change the UID3 of the application). For details on the supported UID ranges, see https://www.symbiansigned.com/app/page/uidfaq
- When building DLLs, Carbide.vs 2.0.1 defaults to building unfrozen DLLs. To ensure that phone (GCCE) builds are succesful, make sure that you have EXPORTUNFROZEN in the .mmp file. If you want to build frozed DLLs in Carbide.vs, see the Online Help for details. If you need to build DLLs, you also need to apply the S60 3.0 SDK patch supplied with Carbide.vs 2.0.1. For details on the patch, see the Release notes.