Hi Erel,
since so many users had (and still have) problems activating the .Net CF2 support (me too...) would't it be good to approach a different way of selecting this feature?
I'm thinking of something like this:
- provide the Basic4ppc.exe.config and Dbasic.exe.config with the default installation
- add a menu option to the IDE (dektop and device) to switch between the both .Net versions (.Net CF 1 should be still the default for new projects)
- save this option to the .sbp file, so every project remembers it's state
- when a project is compiled and .Net CF2 is selected, automatically generate a ApplicationName.exe.config
What do you think?
specci48
since so many users had (and still have) problems activating the .Net CF2 support (me too...) would't it be good to approach a different way of selecting this feature?
I'm thinking of something like this:
- provide the Basic4ppc.exe.config and Dbasic.exe.config with the default installation
- add a menu option to the IDE (dektop and device) to switch between the both .Net versions (.Net CF 1 should be still the default for new projects)
- save this option to the .sbp file, so every project remembers it's state
- when a project is compiled and .Net CF2 is selected, automatically generate a ApplicationName.exe.config
What do you think?
specci48