PowerToTheBuilder.com

I like to explain it this way: Languages have syntax and they have vocabulary. Syntax is rules-based (are they case sensitive, how are statements terminated or continued, what are the keywords and operators). Vocubulary has to do with the properties and methods of the underlying *system* or framework classes. In the case of .NET, VB and C# have ... See Morevery different syntax, but they both sit on top of the same .NET framework classes - hence the vocabulary is similar across languages.
What this means is you can build pretty much anything with any of the .NET languages. Most of the capability and the learning is understanding the underlying .NET framework namespaces and classes. The differences are mostly minor now.
When I last developed in PB (PB 6 or 7) and moved to .NET, I was overwhelmed by the vast number of .NET framework classes and namespaces compared to PB system classes. Over time, the the .NET framework has continued to expand.
Where there were only dozens of PB system classes, there were hundreds and now thousands of classes in the .NET framework.

With .NET, there are so many things you can do by leveraging the underlying power of the .NET framework. Code in the framework is code you don't need to write. In order to do some of these things in PB, you either need to write a lot more code, or you need to leverage third-party libraries. Or PB needs to vastly increase the number of system ... See Moreclasses.
In theory, with PB.NET, Powerscript simply becomes another language that can leverage the full power and functionality of the .NET framework. PB developers can now leverage all of the code in the underlying framework namespaces and classes. The syntax remains Powerscript. The vocabulary becomes .NET

Take a look at this image: http://www.facebook.com/photo.php?pid=2775799&id=103506494680

Office 2007 menu & PB Web Version advance GUI :D..

Everything

send me an email at brad.wery@PowertotheBuilder.com

Okay..Thx B4.. ^_^