G
G. Tarazi
Well, if I was able to say SelectSingleNode("/xyz").Text , and the compiler
was able to verify that "/xyz" is correct according to the schema, I won't
be complaining here today.
It is nice to access the InfoPath document using xpath, but it is ugly that
this is the only option available.
When a Microsoft C# evangelist goes to a script developer, he tries to wow
him, hey, the C# compiler will verify your code, and if the object name was
called "abc" and you were trying to assign "abx" a value, instead of "abc",
the compiler will catch that!
Well, it is in any modern language (Not in InfoPath of course, modern
prehistoric), but that's not all, if your variable is integer, and you try
to assign it with string, a modern programming language will catch that too
(not in InfoPath again).
The above are primitive rule, its like we are born today having them, they
are in any modern programming language, including C#, unless you start
coding for InfoPath and C#, even the most primitive development rules are
ignored.
I guess it is also developed by people from outside MS, I mean InfoPath,
well, it is the only explanation why the were never able to here Mr. Steve
Ballmer yelling "Developers, Developers, Developers, !!!!"
I don't know, but if my boss will yell that developers are the most
important to him, I will have it in mind when developing my products.
What about intllisense, yes, that nice feature that Microsoft was showing
around in the faces of everyone long time ago? "Look, we have intlisence,
our competitors don't, see how easy it is to develop with our products"?
Where is that today InfoPath? where is intlisens on the Xpath expressions?
was able to verify that "/xyz" is correct according to the schema, I won't
be complaining here today.
It is nice to access the InfoPath document using xpath, but it is ugly that
this is the only option available.
When a Microsoft C# evangelist goes to a script developer, he tries to wow
him, hey, the C# compiler will verify your code, and if the object name was
called "abc" and you were trying to assign "abx" a value, instead of "abc",
the compiler will catch that!
Well, it is in any modern language (Not in InfoPath of course, modern
prehistoric), but that's not all, if your variable is integer, and you try
to assign it with string, a modern programming language will catch that too
(not in InfoPath again).
The above are primitive rule, its like we are born today having them, they
are in any modern programming language, including C#, unless you start
coding for InfoPath and C#, even the most primitive development rules are
ignored.
I guess it is also developed by people from outside MS, I mean InfoPath,
well, it is the only explanation why the were never able to here Mr. Steve
Ballmer yelling "Developers, Developers, Developers, !!!!"
I don't know, but if my boss will yell that developers are the most
important to him, I will have it in mind when developing my products.
What about intllisense, yes, that nice feature that Microsoft was showing
around in the faces of everyone long time ago? "Look, we have intlisence,
our competitors don't, see how easy it is to develop with our products"?
Where is that today InfoPath? where is intlisens on the Xpath expressions?