i just don't get how they do it with straight face "oh, to use our pro version, you gonna just plunk down.... 20K. That's a small charge for you guys, yeah?"
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/3836?src=pr&el=h1) Report > Merging [#3836](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/3836?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/47af462d20db9a0310d6333ad08dcf72e5a42de4?src=pr&el=desc) will **increase** coverage by `0.04%`. > The diff coverage is `n/a`.
This is a special request - I need to test the new installer on as many machines as we can, to ensure I've not done anything insane and that it will in fact work across:
Per-user install Admin-elevated install
32-bit install 64-bit install
As many different Windows versions as possible As many different Office versions as possible
The installer already has been tested on for both per-user and admin-elevated:
> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/3836?src=pr&el=h1) Report > Merging [#3836](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/3836?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/47af462d20db9a0310d6333ad08dcf72e5a42de4?src=pr&el=desc) will **increase** coverage by `0.04%`. > The diff coverage is `n/a`.
Computer\HKEY_CURRENT_USER\Software\Microsoft\VBA\VBE\6.0\Addins64 is for 64-bit hosts; 32-bit hosts will be looking for add-ins under Computer\HKEY_CURRENT_USER\Software\Microsoft\VBA\VBE\6.0\Addins
@Hosch250 looks like they might even consider remote...
Hey folks, want to work on my team in Visual Studio?
We'll consider remote for strong senior candidates. https://twitter.com/Pilchie/status/973297544427069440
> After mulling over the results shared by @retailcoder there are few things I didn't anticipate. The work was based on the answer in the SO thread: https://stackoverflow.com/questions/34330668/inno-setup-custom-dialog-with-per-user-or-per-machine-installation?lq=1
However, this apparently didn't factor COM registration and permissions when running elevated.
As it is, if one runs the installer with "Run as administrator", and proceed to install for oneself only, the result is a broken inst
@Hosch250 recall I've interviewed clowns who has been teaching courses on Microsoft technology and has multiple certifications and couldn't answer few basic questions about C#.
the word "senior" is very relative. If you have the chops, they'll see it.
@this FWIW, they have a few people in Texas. I'm going to ask if I can move down there if I have to relocate because it's so much cheaper than Washington.
So, we are now selectively showing errors on a certain widget. One single error is supposed to be shown immediately and others of equal importance are not...
Exactly. Much more safer. He's outside the organization, so no worries about getting stabbed in the back and I get to do all the backstabbing (recall how he turned on the emperor).
So easily that I'll probably cast my last vote for him to give me a bigger say in the new candidates (just like I didn't vote for Jamal and 200 in the first election because I knew they'd win).
Better increase my activity on the site. Might want to consider running.
@Hosch250 but you've been very active, used multiple languages and frameworks.... And more importantly, you've been working on tools for MS IDEs and you've been heavily involved in code review.
That 0 line number is ambiguous - use line labels instead, e.g. BeginningOfLoop: - that way On Error GoTo 0 won't get your code into some weird funky state, or worse, into an unfortunate infinite loop. Line number 0 should be illegal to use... please loose that habit! — Mathieu Guindon21 secs ago
we need an inspection for line number 0 apparently
> From [this SO post](https://stackoverflow.com/q/49364446/1188513):
```vb For i = 2 To LR 0 If Cells(i, 1) <> x Then Cells(ALR, 3) = x ALR = ActiveSheet.Range("C" & Rows.Count).End(xlUp).Row + 1 x = x + 1 Else x = x + 1 End If
If Cells(i, 1) > x Then GoTo 0
If Cells(i, 1) = x Then x = x + 1 End If Next i ```
That stray `0` is a fully legal line number, and it's dangerous. A beginner that makes it a habit of
cos when they are doing that, they usually intend to restart the loop or something. So it's not just the line number 0 but potentially any line number used as the target.
line number 0 on itself is atrocious enough to have its own inspection.
it's funny - if you consider that VBA was meant to be easy for noobs to get started programming. Yet they've made it equally easy for noobs to shoot their feet off.
Thank you for explaining and showing to plenty of people (including me) that VBA is a normal language (and not a "funny" scripting thing or the bastard of programming languages) and writing a good code does not depend on the language, but on the one's abilities to program.
Cheers!
@IvenBach To be fair, it's easy to riff on VBA but I honestly doubt anyone could have been able to write anything remotely similar to Rubberduck back in the 90s.
at least not without requiring a lot of horsepower that wasn't common back then.
ergh. VBA will let you define a numbered line/label as &hFFFFFFFF which the VBE resolves/autocorrects to -1. In that case, On Error Goto -1 actually goes to the line numbered with -1 — ThunderFrameSep 20 '16 at 0:08
> Inspired by the issue #3846, this inspection should deal with the problem of using line numbers as target of `GoTo`. Normally `GoTo` is a big code smell but one common idiom is to use it as a mean to restart an iteration in a loop because VBA has no `Break` or `Continue` equivalent.
However, this is not helpful....
``` 130 For i = 0 to 10 140 Debug.Print "Start of loop" '... lot of code.... '380 If Lame Then '390 GoTo 140 '400 End If '... more code.... '590 Next ```
I like the idea of transposing an ADODB recordset to C#... I'll try to take a moment to review your code later. So.. you know both VBA and C# huh... if you're ever looking for an open-source project to contribute to, I know one that could use your help! — Mathieu Guindon ♦29 secs ago
Ok, i have a dumb question.... for Visual Studio configuration do I really need a Debug32 and Debug64 with the CPU hard-set, or do I just need a Debug and set the active CPU accordingly?
i have a project that was built as a Any CPU and blows up when trying to using System.Diagnostic.Process on a 64-bit process, making it a total lie. (AIUI, Any CPUshould have had made it run 64-bit on a 64-bit OS... but whatever.)
so now trying to figure the best way to explicitly build x86 & x64
Hello Pond... this may be more of SO question in which case I will slink off but I am trying to use evaluate to write a formula result to a range and am getting #value, maybe because of the relative references. The formulaR1C1 works
Sub Macro2()
Dim namedRange As Range Set namedRange = Range("$A$109:$E$209")
With namedRange .Offset(2, 1).Resize(.Rows.Count - 2, .Columns.Count - 1).FormulaR1C1 = "=LN(R[-103]C/R[-102]C)" .Offset(2, 1).Resize(.Rows.Count - 2, .Columns.Count - 1) = Evaluate("=LN(R[-103]C/R[-102]C)") End With
End Sub
Any pointers on how I can move from putting formulas in the range to simply evaluating the results and writing to the range? Without a loop?
Thank you for explaining and showing to plenty of people (including me) that VBA is a normal language (and not a "funny" scripting thing or the bastard of programming languages) and writing a good code does not depend on the language, but on the one's abilities to program.
Cheers!
VBA Rubberducking
VBA Rubberducking