_Application.Run(Object, Object, Object, Object, Object, Object, Object, Object

Re:_Application.Run(Object, Object, Object, Object, Object, ... by ivolimmen on Monday January 10, 2022 @04:47AM (#29872463)

This is exactly why I dropped using C# and wend back to Java. Documentation on Microsoft products is really bad sometimes.

EDIT: Thanks for the downvotes. I am a professional software engineer for hire and in each company this is EXACTLY the issue: documentation. You want me to help you build software? Fine: give me your documentation. Complain about the fact that it takes 2 months to properly understand your software and business rules? Improve your documentation.

[ Parent | on HN ]

Re:_Application.Run(Object, Object, Object, Object, Object, ... by sloucher on Monday January 10, 2022 @05:38AM (#29872823)

This is simply describing a method in the Excel object library, which is not implemented in C#. The method pre-dates C# by many years.

FWIW the place to look for documentation of Application.Run is here: https://docs.microsoft.com/en-us/office/vba/api/excel.applic...

[ Parent | on HN ]

Re:_Application.Run(Object, Object, Object, Object, Object, ... by tanseydavid on Monday January 10, 2022 @01:36PM (#29879335)

I think that the complaint was about MS technical documentation which is justified IMHO.

MS technical documentation has always been more concerned with quantity over quality.

[ Parent | on HN ]

Re:_Application.Run(Object, Object, Object, Object, Object, ... by futharkshill on Monday January 10, 2022 @04:57AM (#29872522)

This has nothing to do with C#. The javadoc for this exact problem would have been identical

[ Parent | on HN ]

Re:_Application.Run(Object, Object, Object, Object, Object, ... by ivolimmen on Monday January 10, 2022 @04:59AM (#29872539)

I agree that the DCOM interface by IBM (20 years ago?) was just as bad... but if the source does not provide any documentation how can you be more clearer if you open it up in another language?

[ Parent | on HN ]

Re:_Application.Run(Object, Object, Object, Object, Object, ... by livinglist on Monday January 10, 2022 @05:35AM (#29872794)

Microsoft probably has the best doc I have every seen compared to Apple…

[ Parent | on HN ]

Re:_Application.Run(Object, Object, Object, Object, Object, ... by formerly_proven on Monday January 10, 2022 @09:05AM (#29874955)

Around ten years ago I would have agreed, MSDN was fairly nice, pretty comprehensive even if a bit full of seemingly autogenerated descriptions like "FrobnicateBar: Frobnicates the bar and return result" at the edges. Nowadays? Not so much.

[ Parent | on HN ]

Re:_Application.Run(Object, Object, Object, Object, Object, ... by sumtechguy on Monday January 10, 2022 @11:29AM (#29877261)

With MSDN docs the older the doc the better it is. Pick something from the early days of win32 and it is a 10 page doc, very well done. Pick something they made up last month and you usually get very basic things. It has been that way for a long time. I remember the orig .NET docs were terrible to use. They have improved decently over the years. I can not prove it but I suspect the docs are only improved when a support case necessitates it.

[ Parent | on HN ]

Re:_Application.Run(Object, Object, Object, Object, Object, ... by rightbyte on Monday January 10, 2022 @04:56AM (#29872517)

It is an internal function though. It is just marked as "reserved for internal use".

[ Parent | on HN ]

Re:_Application.Run(Object, Object, Object, Object, Object, ... by cm2187 on Monday January 10, 2022 @05:43AM (#29872862)

The public version is identical

https://docs.microsoft.com/en-us/office/vba/api/Excel.Applic...

The args have to be object/variants, as it is the values for the sub that will be called and they can have any type. You would use generics today but keep in mind this is 1990s API.

[ Parent | on HN ]

Re:_Application.Run(Object, Object, Object, Object, Object, ... by ivolimmen on Monday January 10, 2022 @04:57AM (#29872524)

That's even worse...

[ Parent | on HN ]