Devart Forums

I was thrilled when I saw, that you can create actual VS projects for your databases.
However, project system is very disappointing, as you cannot open e.g. a table script in the table editor.
It will only open the code editor.
This is not good because the "original" should be the script file in the project, NOT the database object.
You cannot versionize db objects, thus you are either without all those fancy db object editors, or you have to sync DB and scripts and pray you don't mess it up...

I am in the middle of deciding if we partially switch to your tool.
Having both VS' SCC (source control) and all editors working for scripts AND database are pretty much mandatory or we could just stick with our current tool.

Same question as in the other thread:
Will customers of the current 2.55 get this feature?
If yes, any rough time frame?

If we get access full designer support for script files by purchasing 2.55, even if it may just appear in months, I had no problems buying right now.
To me this looks right now like an *extremely* promising product that is just not /there/ yet.

Phew... that read much harsher than I wanted it to read...

Don't get me wrong: It really is a great tool.
I ordered 2 copies of the VS version for further testing.

However, things like not being able to update a current db or use the scripts as the original source (thus not being able to use the fancy editors w/o constant resynching) makes the VS project thing less useful, IMO.

Again I say, we plan to develop this feature. But it's big one. Customers of current 2.55 version won't get it.

Duke wrote:Again I say, we plan to develop this feature. But it's big one. Customers of current 2.55 version won't get it.

As I said, I bought it and me and my colleaque (the other tester) like it very much.
It does not do everything I need or not as smooth, so I still have to fire up my previous Oracle IDE (PL/SQL Developer) sometimes.
However, I can see myself suggesting to replace the old IDE with your next version with these features (SCC, visual designer for files,...).

Until then, I can play with 2.** myself.