Freezing the DLL is required in case to prevent the backward compatibility with the already published DLLs. If your DLL is still under development just put the EXPORTUNFROZN in the MMP, delete the already existing .def file and do the required changes. After the development process remove the EXPORTUNFROZEN from the MMP and Build - Freeze -Build again.
Caution: If the DLL has been published then changing the Frozen DLL is not recommended.
Forum posts: 1134
The freezed API is specified in the .def files.
Its just a text file, and it is possible to edit them by hand if needed, or just simply delete it.
If you havn't yet published the API there is no problem doing this.
Forum posts: 61
Freezing the DLL is required in case to prevent the backward compatibility with the already published DLLs. If your DLL is still under development just put the EXPORTUNFROZN in the MMP, delete the already existing .def file and do the required changes. After the development process remove the EXPORTUNFROZEN from the MMP and Build - Freeze -Build again.
Caution: If the DLL has been published then changing the Frozen DLL is not recommended.