General

Re: VB.NET and C#

Patrick Halstead — Mon, 23 Jan 2006 09:12:49 GMT

Hi Rick,
Yes, it was a tough decision. Don't remember the pros and cons. Anyway, jscript is getting deprecated. C# and VB.NET are preferred in Office 12. More later...

Patrick Halstead [InfoPath MVP]
InfoPathDev

Re: VB.NET and C#

rickhan — Sun, 22 Jan 2006 01:03:41 GMT

When your major corporate clients request reusable code that their people can use for Office automation, it's gonna be VB.Net.
If I was still working back at Microsoft, I'd be using C#.
Being a long term Microsoftie, I would never touch anything related to java(not a bad language, just too much bad history). Never could understand why they chose jscript as the default language for an Office product like Infopath, with most of the example code in jscript. I could see having both, with vb as the default. Then when .NET support came out, switching to C# as the default code for examples.

Re: VB.NET and C#

Matt Faus — Sat, 21 Jan 2006 18:13:50 GMT

Haha, I just can't get over the lack of grouping symbols, such as brackets and parentheses! I love brackets!

---------------
Matt Faus
InfoPath Dev Texas

Re: VB.NET and C#

rickhan — Sat, 21 Jan 2006 06:39:29 GMT

Managed code is what I'm interested in, either in VB.NET or C#.NET
Has to fit in with all the other Office automation that is a part of this project. JScript is not worth considering for Office automation, if you could even use it.
VB.NET can be very structured -- I write classes in it and data structures, and there are many more vb.net programmers out there than C#. VB.Net produces the same run time code as C#.NET and C++.Net .

Re: VB.NET and C#

Matt Faus — Wed, 18 Jan 2006 02:13:48 GMT

quote:
Originally posted by rickhan

The preferred language is VB.Net , with C#.Net as secondary.
Absolutely no demand for jscript or vbscript.

Where are you getting this information from? It sure doesn't match up with what I've observed.

Personally I think VB, Visual Basic, is just that - Basic. Although it might be much easier understood by non-programmers (Information Workers) that create scripts and small programs to ease the flow of their day-to-day activities, C# and JScript (both very structured languages) provide a much cleaner and easier understood source code, especially for large projects. However, this is just my opinion. Also, there is a very big difference between managed code and the script languages.

Regardless, sorry that there are not as many VB.Net examples! Maybe we can convert the examples we have now to show several languages.

---------------
Matt Faus
InfoPath Dev Texas

VB.NET and C#

rickhan — Tue, 17 Jan 2006 23:17:44 GMT

I'm seeing the adoption of InfoPath by many medium to large businesses, mainly using InfoPath to store collected in SQL and to edit it.
The preferred language is VB.Net , with C#.Net as secondary.
Absolutely no demand for jscript or vbscript.
Since all my projects are using MS Office automation and SQL, all the programmers doing work for me use VB.Net. It's a quickly growing market.

So why all the samples/examples in jscript and no indepth SQL (using joins, etc) documentation? And maybe some advance formatting of reports, etc.

What you have done is a great start so far, and I appreciate it. Looking forward to more advanced solutions...