A graphical language for business rules is not a good idea. I would avoid it Business rules have lots of if checks and loops in them, which don't visualize well.
You're much better off with a textual language for describing business rules.
To get a phenomenial user experience for editing code you need:
- A parser with good error recovery
- The ability to do incremental re-compilation
Good error recovery allows you to effectively determine programer intent from syntatically incomplete constructs. That's crucial for implementing intellisence.
The ability to do incremental-recompilation gives you the ability to do efficent background compilation in response to user edits.
The easiest way to get good error recovery is to write your parser by hand. That way you can use whatever amount of look ahead, or algrorithmic rules, for figuring out what to do in the presence of syntax errors.
When you use a parser generator to create your parser, you loose a lot of flexibility in dealing with syntax errors. That flexibility makes the difference between a good intellisence expereince and a crapy one. So, I recommend you just write it by hand using recursive descent.
Implementing efficent re-compilation requires you to be able to :
1) Properly break down semantic analysis into phases (for something like C# this would be: first construct namespace and type symbols, then resolve using statements, then resolve base classes, etc).
2) The ability to construct a phase-aware dependency graph
3) Algorithms for processing the dependency graph, and invalidating parts of it in response to user edits
For full-flegged programing language, implementing re-compilation can get really tricky. In your case, because you are describing business rules, it might be much simpiler for you (or if compilation is quick enough you might not even need it).
So, I would start with the parser, and then build intellisence on top of it.
If you can avoid VS integration, I would. Integrating into VS requires A LOT of plumbing, and the interop is likely to cause headaches. There are a few companies that sell windows forms editor controls that you hook your parser up to. That are much easier to integrate with than VS.