0

If there is any compilation error, developer console does not show errors and what is more confusing is that it does not report that save was not successful. There is also no feedback on successful message other than the asterisk in tab for the unsaved files.

2
  • It's not any error, but I've seen some odd behavior myself, like editing a VF page that compiles in Force.com IDE but won't save in the browser IDE.
    – sfdcfox
    Commented May 10, 2014 at 23:53
  • It's probably a good idea for you to think of moving to a real IDE.
    – dphil
    Commented May 12, 2014 at 14:44

1 Answer 1

1

I have been observing some odd behaviors as well. However a big negative with the developer consoles which compelled me to move away from it for the time being until it stabilize are.

CONS
1. It Overrides the code. As compared to force.com IDE, which gives warning if page on server have been updated by some body else.
2. Save/compilation issue as you mentioned.
3. Developer console is being too heavy for the browser to handle efficiently, resulting it being slow.
4. Most of the time if debug logs are large it doesn't load them at all and gives error.

PROS
As of now I use it for following only.
1. To check the line-by-line test coverage of the classes, as there is no other alternative now.
2. RUN some quick queries and update them, then and there.
3. Anonymous execute apex.

1
  • You can use the tooling API to get the line-by-line test coverage. I've done so in the FuseIT SFDC Explorer. So the "there is no other alternative now." isn't true. :) Commented May 12, 2014 at 20:49

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .