I can't write an ActiveX script in VB.net so that I can execute it
with SQL Server JOBS
I can't write an ActiveX script in VB.net so that I can execute it
with SQL Server JOBS
I can't write an ActiveX script in VB.net so that I can execute it
with SQL Server JOBS
I can't write an ActiveX script in VB.net so that I can execute it
with SQL Server JOBS
I mean.. why is .NET still HALF-BAKED?
- Show quoted text -
SQL Server 2005 supports Stored Procedures written in the CLR language
of your choice: C#, VB.NET, J#, C++.NET, or any other .NET language.
So what's your point?
And I'm running .NET applications on Windows 2000 just fine, with no
performance problems whatsoever. As with any development lifecycle,
you have to profile the application, and identify the slow points, and
optimize them. It wouldn't matter what language, database, or
development platform you were working with.
..NET is far more secure, type-safe, and robust than VB6 *ever* was. It
forces me to write higher quality code by paying attention to what I'm
doing. VB6 produced an entire army of cowboy coders who are now, to
put it bluntly, pissed off that Microsoft wants to encourage folks to
write more secure, stable code using a development platform that
encourages secure, stable code.
As far as I'm concerned, it can go the way of the dodo. It's only use
now is for maintaining legacy applications. We've gradually ported
every VB6 application we had to .NET, and we've seen nothing but
improvements in performance, stability, and maintainability. I can't
possibly see how that's a bad thing.